Deploying changes to individual Lambdas using Serverless Framework

I have a serverless project that deploys 2 Lambdas in the same stack: service: example-apis2 provider: name: aws memorySize: 512 region: us-west-1 apiGateway: restApiId: ${env:APIGWID} # API Gateway to add this api to restApiRootResourceId: ${env:RESOURCEID} functions: example2: handler: index2.handler layers: – arn:aws:lambda:us-west-1:[myaccountid]:layer:example-layer:1 events: – http: path: api2 method: get example3: handler: index3.handler layers: – arn:aws:lambda:us-west-1:[myaccountid]:layer:example-layer:1 …

Deploying multiple Serverless Framework apis to the same AWS API Gateway

By default, each Serverless project you deploy will create a new API Gateway. In most cases this works fine, but for larger projects you may need to split your apis across multiple smaller Serverless projects, each with their own serverless.yml that can be deployed independently. The Serverless docs describe how to do this here. In …

Serverless Framework: AWS Lambdas with scheduled events and parameters

To configure an AWS Lambda to get triggered by a CloudWatch event, you can use the ‘schedule’ event in your config: functions: your-function-name: handler: your.Handler timeout: 30 events: – schedule: rate: rate(12 hours) input: puzzles : “2” targetGivens : “20” You can also pass parameters from the CloudWatch event when your Lambda is invoked by …