Hi, I want to use
nodegit
in my lambda function, this requires access to the local file system. Does lambda even has a "local file system" or if it doesn't and I need to attach some other AWS resource (s3?) to mimic the fs, can claudia help with that?
You can access the /tmp folder but you can't rely on anything you write there being available on other runs. There's now EFS support in lambda too but I'm not familiar with it yet.
Hi everyone, so I'm facing some problems with claudia bot builder, Does any one know how to fix, what I'm doing wrong ?
'OAuth "Facebook Platform" "invalid_request" "(#100) The parameter subscribed_fields is required.-
Here is my configuration
`
"scripts": {
"create": "claudia create --api-module bot --region eu-west-1 --configure-fb-bot",
"configure-fb": "claudia update --configure-fb-bot",
"deploy": "claudia update"
},
"dependencies": {
"claudia": "^5.12.0",
"claudia-bot-builder": "^4.5.0"
}
`
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?
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.
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
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).
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?
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?
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.