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)...
I want to create a nodejs layer, in order to later create multiple functions that require it.
Is there a way to create the layer using claudia ?I have seen the announcement that linking layers is now supported (5.3), but I could not find info on creating the actual layer.
I'm following the instructions here to create a layer - https://github.com/lovell/sharp/issues/1702#issuecomment-499331245
But I cannot seem to reference sharp from within my lambda. I'm lazy loading it (have tried from 'sharp' and from '../../opt/node_modules/sharp' but I'm getting MODULE_NOT_FOUND. Anyone have any clues?
I'm back to trying to get sharp working with Lambda (having failed previously)
I'm following the instructions here to create a layer - https://github.com/lovell/sharp/issues/1702#issuecomment-499331245
But I cannot seem to reference sharp from within my lambda. I'm lazy loading it (have tried from 'sharp' and from '../../opt/node_modules/sharp' but I'm getting MODULE_NOT_FOUND. Anyone have any clues?
I've finally done it :-D. If anyone is trying to do similar. I created a layer and installed sharp using npm install --arch=x64 --platform=linux sharp.
I zipped this and added it to AWS as a lambda layer. Then I lazy-loaded sharp in my code using
const sharp = require('/opt/node_modules/sharp');
prod URLs work, and everything else doesn't. I'm confused on where to continue.
dev and prod stage to the authorizer, but I doubt that works because the authorizer itself isn't attached to any API gateway.
prod stage doesn't link to the API Gateway like the dev stage.
set-version command, it doesn't create a proper permission policy for that stage. So, I created a command for aws command line.aws lambda add-permission --function-name FUNCTION:STAGE --statement-id web-api-access-STAGE-TIMESTAMP --action lambda:InvokeFunction --principal apigateway.amazonaws.com --source-arn arn:aws:execute-api:REGION:ACCOUNT_ID:API_ID/authorizers/\*
claudia update at least once for that alias
claudia create to set it initially
set-version to reassign a deployed alias
I can't see anywhere if there is an argument to switch yarn instead of npm. I am using
yarn workspaces and try to create a lambda function from a project which depends on another local package in monorepo. npm --production fails to recognize local packages so yarn support would be life saver
When I use the files property in packages.json, claudia is not finding the /var directory. This is the temp directory the package is compiled in. Note, I'm on a mac
Hello!
I'm trying to implement URL redirection on a GET endpoint similar to the example here (https://github.com/claudiajs/example-projects/blob/master/web-serving-html/web.js).
The example:
// because the success code is 3xx, the content will be used as the redirect location
api.get('/redirect', function () {
'use strict';
return 'https://github.com/claudiajs/claudia';
}, { success: 302 });My code :
const APIBuilder = require('claudia-api-builder');
const API = new APIBuilder();
API.get('/token', request => myFunction(API, request), {
success: constants.statusCodes.movedTemporarily, // this is 307
});I've tested it on a browser and the page does not get redirected. The redirection URL simply gets outputted onto the page itself. Any idea on what I may be misunderstanding?
Hello guys, I really enjoy using ClaudiaJS for lambda deployments Thanks for that.
Please, while deploying I see some logs of my App in my terminal, is ClaudiaJS running my handler somehow before pushing it to AWS (at the package validation step)? If yes is it possible to disable this?
1 reply
