claudiajs/claudia

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

constantinov

@constantinov

something like viber/323g2s323

Carl Banbury

@cbanbury

Hi, when using the add-scheduled-event, I want to be able to run it to change an existing schedule.

Currently if I run add-scheduled-event twice with two different --cron defintions, it creates two identical targets in the EventBridge, under one rule...

Am I doing something wrong?

jofg123

@jofg123

Hi, Im a beginner and i want to create chatbot in fb then i have problem with this

Hi, Im a beginner and i want to create chatbot in fb then i have problem with this$ claudia create --region us-east-1 --api-module bot --configure-fb-bot
loading package config sts.optInRegionalEndpoint
Error: connect ETIMEDOUT 169.254.169.254:80
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1129:14) {
message: 'Missing credentials in config',
errno: -110,
code: 'CredentialsError',
syscall: 'connect',
address: '169.254.169.254',
port: 80,
time: 2021-02-08T09:23:06.666Z,
originalError: {
message: 'Could not load credentials from any providers',
errno: -110,
code: 'CredentialsError',
syscall: 'connect',
address: '169.254.169.254',
port: 80,
time: 2021-02-08T09:23:06.665Z,
originalError: {
message: 'EC2 Metadata roleName request returned error',
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '169.254.169.254',
port: 80,
time: 2021-02-08T09:23:06.663Z,
originalError: [Object]
}
}
}

OtterCoder

@OtterCode

So, does anyone have recommendations for doc generation with Claudia?

Kqzz

@Kqzz

Hi, Im a beginner and i want to create chatbot in fb then i have problem with this$ claudia create --region us-east-1 --api-module bot --configure-fb-bot
loading package config sts.optInRegionalEndpoint
Error: connect ETIMEDOUT 169.254.169.254:80
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1129:14) {
message: 'Missing credentials in config',
errno: -110,
code: 'CredentialsError',
syscall: 'connect',
address: '169.254.169.254',
port: 80,
time: 2021-02-08T09:23:06.666Z,
originalError: {
message: 'Could not load credentials from any providers',
errno: -110,
code: 'CredentialsError',
syscall: 'connect',
address: '169.254.169.254',
port: 80,
time: 2021-02-08T09:23:06.665Z,
originalError: {
message: 'EC2 Metadata roleName request returned error',
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '169.254.169.254',
port: 80,
time: 2021-02-08T09:23:06.663Z,
originalError: [Object]
}
}
}

I'm actually getting this exact same problem! I could use some help, if anyone has any ideas.

Nicolás Sosa

@nsosacarrion-osma

Hi! I want to propose a very slight change to claudia. I need to deploy a lambda with the new max memory that is 10240, but we need to change that in src/utils/limits.json.

Victor Wiebe

@victorwiebe

Hello there, I am experiencing CORS issues.

Environment is claudiajs deploying to lambda

I can test properly from Postman

CORS issues on Website itself when testing on localhost:3000

Please advise

Victor Wiebe

@victorwiebe

So Basically, on the website doesnt work, on Postman works perfectly

Sethupathy

@Sethupa14919203_twitter

Map your api gateway url to DNS, will sort out the CORS issue

@victorwiebe

lstone

@lstone

Hello, I'm using Claudia.js and Claudia-api-builder to deploy a Lambda function (works great). Currently this function has API Gateway as an event source. I'd like this same Lambda function to be able to alsp listen to SNS events Additionally, I'd like a specific function inside the Lambda codebase to be invoked upon receiving an SNS event. Is there a way to do this w/ Claudia.js in conjunction w/ the api builder?

lstone

@lstone

Follow up - I've sorted this out ^

Elia Contini

@EliaContini

Hi all,

I'm trying to run the Hello World AWS Lambda Function following the steps in the tutorial.

I ran

claudia create --profile claudia --region us-east-1 --handler lambda.handler

but the output I got is this error

validating package      npm dedupe -q --no-package-lock
npm dedupe -q --no-package-lock failed.

and the file claudia.json is not created.

I'm using claudia 5.13.0, Node.js 14.16.0, npm 7.5.6 on Ubuntu 18.04.5 LTS .

Any suggestion?
Thank you

Bruno M.

@brunosmm

Hello,

I have a web-api project with a few endpoint, and would like to include a new lambda which should be trigger via an event scheduler. Can I add a new js file in the project and set a claudia add-scheduled-event or it should be a new project separated from the web-api?

I tried to find an example of this in the git repo but didn't find any.

Bruno M.

@brunosmm

@lstone Can you share how you did it?

AlfredMadere

@AlfredMadere

I have successfully run the hello world micro instance tutorial but don't see it populate on my aws account when I look in the browser. Am I missing something?

Sam Baek

@sambaek-rapidai

Is there no more active development on Claudia? Running into some problems cause I want to utilize the max memory limits as well as setting up an endpoint as HTTP_PROXY (would love suggestions on if I can achieve the latter through Claudia; my initial research shows that it hardcodes AWS_PROXY making this not possible without forking or updating).

Laith Harb

@harblaith7

I am having troubles throwing errors with different status codes on Claudia. I know with Express JS it would look something like res.status(400).send(), but with claudia its just a return so I'm not sure how to tackle it

koushik110798

@koushik110798

Hello,

I am trying to update my lambda function with following command

claudia update --region us-west-2 --version qa2a --set-env env=qa2 --memory 4096 --timeout 30

But I get the following error

the memory value provided must be less than or equal to 3008

But the lambda function can have memory 10240

Any suggestions would be appreciated

Thank you!

Asaduzzaman Himel

@asaduzzaman69

@gojko does Claudia support web socket api getway~?

Ghost

@ghost~58a7c5ded73408ce4f4b2a6b

claudia create --handler lambda.handler --deploy-proxy-api --region us-west-2 --name fileUploader

packaging files
TypeError: Cannot read property 'replace' of undefined
at expectedArchiveName (/Users/srn/.nvm/versions/node/v13.7.0/lib/node_modules/claudia/src/util/expected-archive-name.js:3:28)
at runWithConfig (/Users/srn/.nvm/versions/node/v13.7.0/lib/node_modules/claudia/src/util/pack-project-to-tar.js:10:56)

I keep getting that error when I try to do claudia create, any ideas why?

I tried changing the node versions, but no luck.

Ghost

@ghost~58a7c5ded73408ce4f4b2a6b

My lambda.js file seem ok too.

Aditya Avanth

@AdityaAvanth_twitter

I get the same error as @ghost~58a7c5ded73408ce4f4b2a6b
packaging files
TypeError: Cannot read property 'replace' of undefined
at expectedArchiveName (/Users/admin/.nvm/versions/node/v14.17.0/lib/node_modules/claudia/src/util/expected-archive-name.js:3:28)
at runWithConfig (/Users/admin/.nvm/versions/node/v14.17.0/lib/node_modules/claudia/src/util/pack-project-to-tar.js:10:56)

Can someone pls help me debug this?

Ryan Davis

@RyPoints

When constructing an AWS Lambda function with Claudia, the docs say to do exports.handler = function (event, context) { and then to reference the payload parameters sent to the function using event.parameterName but when I do that and print the parameters to the console, they all say "undefined." Anyone know why?

I'm pretty sure I have used it before like that. I am wondering if there's been changes since the docs were written...maybe event.somenewsubproperty.parameterName or something?

Ah, nevermind, already figured it out. Alamofire changed a bit and I wasn't passing the parameters.

npwoods

@npwoods

I'm trying to use Claudia.js for Lambda@Edge, but my Lambdas end up being wayyy to large. I tried downloading the Lambda package from AWS, and I see claudia inside my node_modules. I've confirmed that in my package.json, Claudia is a devDependency not a dependency. I'm probably doing something stupid

ziedmahdi

@ziedmahdi

Hello,
I wanted to explore callbackWaitsForEmptyEventLoop parameter so I have created a lambda with the below code

var ApiBuilder = require('claudia-api-builder'),
    api = new ApiBuilder();

module.exports = api;

api.any('/test', function (request) {
    request.lambdaContext.callbackWaitsForEmptyEventLoop = true;

    var prefix = request.proxyRequest.queryStringParameters.id;
    console.log('hello: ' + prefix);
    setTimeout(function () {
        console.log('after timeout: ' + prefix);
    }, 5000);

    return new ApiBuilder.ApiResponse('OK ' + prefix, {'X-Version': '202', 'Content-Type': 'text/plain'}, 200);

});

The strange thing is I don't see the 'after timeout' message.

even on other requests

ziedmahdi

@ziedmahdi

{
  "devDependencies": {
    "claudia": "^5.13.1"
  },
  "dependencies": {
    "claudia-api-builder": "^4.1.2"
  }
}

ziedmahdi

@ziedmahdi

when I tried with callbackWaitsForEmptyEventLoop=false,

var ApiBuilder = require('claudia-api-builder'),
    api = new ApiBuilder();

module.exports = api;

api.any('/test', function (request) {
    request.lambdaContext.callbackWaitsForEmptyEventLoop = false;

    var prefix = request.proxyRequest.queryStringParameters.id;
    console.log('hello: ' + prefix);
    setTimeout(function () {
        console.log('after timeout: ' + prefix);
    }, 5000);

    return new ApiBuilder.ApiResponse('OK ' + prefix, {'X-Version': '202', 'Content-Type': 'text/plain'}, 200);

});

I got 'after timeout' but only when I sent two request (19 sec between each)

When I sent a third request (12 minutes later) the 'after timeout' message didn't appear

ziedmahdi

@ziedmahdi

@harblaith7 the easiest way is to use ApiResponse
return new ApiBuilder.ApiResponse('Request received', {'Content-Type': 'text/plain'}, 200);

Where communities thrive

People

Repo info

Activity