claudiajs/claudia

Deploy Node.js projects to AWS Lambda and API Gateway easily

Gojko Adzic

@gojko

@kevintechie weird, but thanks for letting me know, I can add that to developer docs

Ross Coundon

@rcoundon

I'm trying to package up my typescript lambda project using claudia-api-builder as the entrypoint.
The entrypoint is defined in index.js (as I don't think there's native typescript support yet)

package.json
|--src
  |--functions
    index.js
    handler.ts
|--node_modules
|--build

I'm trying to deploy using this command:

claudia create \
  --region eu-west-2 \
  --api-module build/functions/handler \
  --keep

All the compiled files, including the index.js are written into the build folder which mirrors the structure in src.
However, I get an error

Cannot find module '/var...../package/build/functions/handler

and then:

cannot require ./build/functions/handler after clean installation. Check your dependencies.

Is it possible to structure things in this way? If so, what should my create command be?

Gojko Adzic

@gojko

@rcoundon do claudia pack and see what gets included in the package. Your NPM project setup might be ignoring the build directory

You can see how to set up files to be included or excluded here https://claudiajs.com/tutorials/packaging.html

Ross Coundon

@rcoundon

That was it - thank-you

Simran Singh

@esimran

when I run claudia create --handler lambda.handler --deploy-proxy-api --region us-east-1 I get an Unexpected token { error, I'm using an express app with babel. Any advice on how to fix this? Do i have to transpile the code using webpack first?

Gojko Adzic

@gojko

@esimran try running require('./lambda') from node in that directory

the problem suggests you have a syntax error somewhere

hackerunet

@hackerunet

hi there, I have a question, how can I require an external config file to create a lambda function with claudia?

const jwt = require('jsonwebtoken');
const config = require('../config/config');

exports.auth = function auth(event, context, callback) {
    'use strict';
    console.log('got event', event);

I'm currently getting a config module not found.

"Cannot find module '../config/config'

Ross Coundon

@rcoundon

I'd just like to say, thanks for creating ClaudiaJs. It truly simplifies what can be a very complicated topic of deployment in regards to SAM and/or CloudFormation.

Gojko Adzic

@gojko

@rcoundon thanks!

hackerunet

@hackerunet

if creating microservices isn't any way to avoid handling multiple configurations for each microservice? I really need to have 2 environments for testing and apparently I cannot reference any centralized configuration if the file is out of the project, is there any workaround for this?

Gojko Adzic

@gojko

@hackerunet you can use AWS System Manager to store parameters (check the parameter store) or use env variables or stage variables for APIs

also, check out https://claudiajs.com/tutorials/versions.html

it includes an example of how to include different config files for different environments

hackerunet

@hackerunet

ok, another question, I received an error deploying to AWS, it says the lambda function already exists, so, the main problem is, how can I delete a lambda function that is not listed in the functions list in AWS? claudia complains it exist but I see nothing in AWS

hackerunet@kerberobot:~/Projects/sp-api/auth$ claudia create --name auth --region us-east-1 --handler index.auth
packaging files npm install -q --no-audit --production
npm WARN auth@1.0.0 No description

creating Lambda lambda.setupRequestListeners
{ ResourceConflictException: Function already exist: auth

hackerunet

@hackerunet

sorry for my estupidity, I will never ask anything again.

thanks @gojko

the issue was me checking in the wrong region in AWS console. I'm an idiot.

Ross Coundon

@rcoundon

Hi @stojanovic - Is the best place to report errata and issues encountered with your book on the Manning site or here?

Slobodan Stojanović

@stojanovic

On the Manning site, please. Thanks :)

Kevin Coleman

@kevintechie

Hello, @gojko. I finally submitted a pr with validation and tests for adding authorization scopes to API Gateway methods.

Kevin Coleman

@kevintechie

While adding the authorizationScopes support, I noticed that you don't have "root": true in your .eslintrc.json file. Is this intentional? If not, it would be nice to have so that your config is not augmented by an eslint config higher in the project path.

Slobodan Stojanović

@stojanovic

It’s probably useful to add root: true, thanks for the suggestion

Kerim Incedayi

@cevatkerim

Hi @gojko , I would like add a platform to the bot builder. Should I just submit a PR?

hackerunet

@hackerunet

I have serious issues trying to use claudia with mongoose connector to get mlab database records, I get the following error

{
  "errorType": "string",
  "errorMessage": "event does not contain routing information",
  "trace": []
}

I cannot find a way to build a class to manage mongodb connections for each function, the documentation shows that attempting to create a function to do this needs to use

export const handler = async (event, context) => {
    const db = await connectToDatabase();
    // Do something with it...
};

and basically I'll have to make every function with routing and controllers logic bundled into the database connection handler, any thoughts or documentation regarding claudia architecture patterns? or something related?

Slobodan Stojanović

@stojanovic

@cevatkerim PR is the best way, it would also be great if you can send me a bit more details(i.e., which platform, etc.) in DM and I’ll be able to give you some guidance.

Kevin Coleman

@kevintechie

Hello @gojko , now that pr #199 has been merged, do you have a sense when it will be released to npm?

Gojko Adzic

@gojko

@kevintechie there were a few regression failures when I ran it, mostly because the flag to check for authorization scopes being an array failed if it was blank, so it broke the other cognito authorizer tests; I fixed that and re-ran the test suite, as soon as it completes I'll publish it

it takes a few hours to run, so tonight most likely

just got a notification that it finished successfully, so publishing now

Gojko Adzic

@gojko

@kevintechie it's on NPM now, as 5.7.0
is this OK as an example for how to use it? https://github.com/claudiajs/claudia-api-builder/blob/master/docs/authorization.md#adding-authorization-scopes-to-cognito-authorizers

Kevin Coleman

@kevintechie

Yes, perfect. That's exactly how we're using it in our code.

Gojko Adzic

@gojko

thanks for this patch

Kevin Coleman

@kevintechie

Sorry for the bug. Can't wait for optional chaining. https://github.com/tc39/proposal-optional-chaining

Gojko Adzic

@gojko

@kevintechie no worries, that's exactly why we have so many automated tests :)

Chardine

@Chardine

Hello, does claudiajs have support for websockets?

Bill Hainaut

@billhainaut

If I want api.get('/sumpin', xxxx) to get mapped to /v2/somename/sumpin how do I make that happen with ApiBuilder? Are there options for the name of the resource/sub-resource?

raedwa01

@raedwa01

so with cognito authorizer, can I make it so the unauthenticated users are able to run certain apis and authenticated users are able to run others but no one can run our apis without something from cognito first?

Gojko Adzic

@gojko

@raedwa01 you can use an IAM Authorizer and set up two roles in cognito for authenticated and unauthenticated pools

@billhainaut you can do that with api gateway custom domains, where you can assign domain/prefix to an API Gateway stage. claudia doesn't add any specific features to that, because it's trivially easy to set up a custom domain using the existing aws cli tools or the web console. check out https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html

@Chardine web sockets are not supported at the moment

Primož Verdnik

@drye

@gojko when using claudiajs with aws-serverless-express - would it be still possible to use API gateway's Usage Plans for per-endpoint throttling? I assume not, since API gateway is just serving as a proxy?

Chant Long

@chantlong_twitter

@gojko

@chantlong_twitter we added something in 5.6 that lets people use STS tokens and assumed roles, but that picks up AWS_ROLE_ARN from the environment and thinks that you want to use STS if it is defined

Sorry for the late reply. I just happened to have AWS_ROLE_ARN in my bash profile which is used in my other repos not related to the claudia repo. I could change the env name so I can use 5.6 Thanks. I use AWS_ROLE_ARN for other parts of the aws-sdk methods like IAM methods

Subbu

@subbu-everest

Greetings!

How to update the security-group and subnets attached to the Lambda function.

I can attach security-group and subnets while creating the function using --security-group-ids and --subnet-ids flags respectively.

How to update them?

Gojko Adzic

@gojko

@subbu-everest use the aws CLI tools for that. In general, claudia does not re-implement aws cli commands where it can't provide additional value. check out https://docs.aws.amazon.com/cli/latest/reference/lambda/update-function-configuration.html - if you used an alias when creating the function, you may also need to republish the alias after updating the VPC configuration for it to take effect. you can do that with claudia set-version --version <ALIAS>

Subbu

@subbu-everest

That makes sense. Thank you @gojko

Where communities thrive

People

Repo info

Activity