Less-Framework | An adaptive CSS grid system | Grid library

I'm trying to mount an EFS to my Lambda function so that I can use large dependencies. So far I've been following this tutorial.

I slightly modified the .yml.

Disclaimer: I admit this is more of a broad-ish best practice question, rather then a specific programming issue, however, I believe the SO bunch is the best audience for it. I am aware of this similar question (Should I be using Express.js in a Serverless app?), but the answers don't seem to answer mine.

I want to move an Express.js from AWS Lightsail/EC2 to serverless for typical reasons, and Lambda is my weapon of choice. However, a whole framework together with an app on top of it may be a bit hefty to be still considered a function and so possibly unsuitable to be run as such on AWS Lambda, or Google/Azure Functions. While I'm convinced it is doable, is it a good idea? Wouldn't this setup kill efficiency and complicate handling things such as sessions states, ultimately defeat the purpose of serverless functions?

I am trying to create a basic example of using API Gateway WebSocket connecting to an AWS Lambda function.

I followed the example from this link.

The goal is to have one Lambda csproj with multiple entry-points (functions), same as specified in the example above.

API Gateway:

I have four routes, all of them connecting to the same lambda function: cgavan-websocket-2:

• $connect
• $disconnect
• echo
• $default

Lambda function:

I have a lambda project with four different functions:

• Connect.FunctionHandler(APIGatewayProxyRequest request, ILambdaContext context)

• Disconnect.FunctionHandler(APIGatewayProxyRequest request, ILambdaContext context)

• Echo.FunctionHandler(APIGatewayProxyRequest request, ILambdaContext context)

• Default.FunctionHandler(APIGatewayProxyRequest request, ILambdaContext context)

Question:

How can I specify, for each of the API Gateway routes, which function handler to invoke from the Lambda csproj?

Right now, when I connect to the API Gateway WebSocket (with the WebSocket Request Route: $connect), it always invokes the Default.FunctionHandler().

Hey I was following this blog post - https://www.serverless.com/blog/publish-aws-lambda-layers-serverless-framework which creates gif from video files using ffmpeg.

My file structure -

gifmaker

• layer
  • ffmpeg library
• handler.js
• serverless.yml

My handler.js code -

I'm using AWS CodeBuild to deploy the function to AWS lambda using serverless-framework.

Here is my buildspec.yml,

So what I'm trying to do is to dockerize a Flask REST API that uses Serverless and DynamoDB. I followed this tutorial but it doesn't mention about dockerizing the whole thing. I've also tried to do some research and came up with very minimal resources, like this for example.

Is this even possible? If so, some links to guides/advice would be helpful. Thanks.

I'm trying to add a hold job into a workflow in CircleCI's config.yml file but I cannot make it work and I'm pretty sure it's a really simple error on my part (I just can't see it!).

When validating it with the CircleCI CLI locally running the following command

circleci config validate:

I get the following error

Error: Job 'hold' requires 'build-and-test-service', which is the name of 0 other jobs in workflow 'build-deploy'

This is the config.yml (note it's for a Serverless Framework application - not that that should make any difference)

I'm trying to do some transitive file references in my serverless.yml, but it seems like serverless always resolves references based on the serverless.yml file regardless of where other referenced files live. Example:

serverless.yml:

I would like to start using serverless-framework to manage lambda deploys at my company, but we handle PHI so security’s tight. Our compliance director and CTO had concerns about passing our AWS key and secret to another company.

When doing a serverless deploy, do AWS credentials ever actually pass through to Serverless, Inc?

If not, can someone point me to where in the code I can prove that?

Thanks!