@suraj_datta_twitter is this express? Logs work for all stages.
I tried installing the offending as an optional dependency and passing
--no-optional-dependencies
How do other Lambda implementations deal with this, then?
2 replies
async function zipData(content: string): Promise<Buffer> {
return new Promise((resolve, reject) => {
const filename = `/tmp/${new Date().valueOf()}.zip`;
const dataBuffer = Buffer.alloc(content.length, content);
const output = fs.createWriteStream(filename);
const archive = Archiver('zip', {
zlib: { level: 9 },
});
output.on('close', () => {
async function asyncWorker(): Promise<Buffer> {
return await readFileAsync(filename);
}
asyncWorker()
.then((output) => {
return resolve(output);
})
.catch((err) => {
return reject(err);
});
});
archive.on('error', (err) => {
log.error('zipping archive error', err);
return reject(err);
});
archive.pipe(output);
archive.append(dataBuffer, { name: 'data.csv' });
archive.finalize();
});
}
I managed to get my Github workflow working:
#!/usr/bin/env bash
mkdir -p ~/.aws
cat > ~/.aws/credentials << EOF
[deploy]
aws_access_key_id=$AWS_ACCESS_KEY_ID
aws_secret_access_key=$AWS_SECRET_ACCESS_KEY
EOF
export AWS_PROFILE=deploy
./node_modules/.bin/claudia update --no-optional-dependencies --version livevalidating package npm dedupe -q --no-package-lock
npm ERR! code EEXIST
npm ERR! Refusing to delete /tmp/LADlqq/xxx/package/node_modules/claudia/node_modules/.bin/mkdirp: is outside /tmp/LADlqq/xxx/package/node_modules/claudia/node_modules/mkdirp and not a link
I cannot fix this anyway. I use claudia in docker with lambda image. This worked without a problem up till now. But after I updated dependencies this started to happen
this is the command with which I run it:
claudia update --source dist --handler scripts/lambda.handler --use-local-dependencies --role api-deployment-executor --use-s3-bucket lambda-uploads --memory 1024 --timeout 300 --deploy-proxy-api --region eu-central-1 --config bin/deploy/claudia-dev.json --name app-api-staging
using claudia 5.12.0
if (isLambda) {
// You're on AWS Lambda
module.exports = app;
} else {
// Local or elsewhere
app.listen(3000);
}index.js does not export method handler
Create another file for running the Express server locally. For example, app.local.js, similar to the one in this example: https://link.medium.com/upJrZSfaq6
it says deployment package too large
Is there anyway I can seperate my api routes into seperate aws lambda function
but I see most of the size is due to node_modules
Is there any benefit of using 1 lambda function for app vs seperate aws lambda function for each route ?
I was wondering how do I deploy it as seperate lambda function from my express app. The only way I see is to go in aws and create functions there
If you want to have your app in AWS Lambda fast, deploy your express app directly, then start splitting it.
There are many benefits. Smaller apps are faster (you probably heard about cold start, it almost doesn’t not exist with small lambdas). It’s easier to debug (logs will be separated by routes)...
thanks for your response
any article you can direct me to achieve that ?