Serverless and Lambda
I’ve been working more with serverless projects using stuff like AWS Lambda or Azure Functions. Very handy indeed: easy to deploy and then use. Sometimes though, you want a little more: you need an S3 bucket or want API Gateway in front of the Lambda function. Enter serverless!
The Serverless Framework allows for easy deployment of your Lambda and other services by just describing your infrastructure in a serverless.yml file. You can define what API Gateway endpoints you need and which Lambdas they can point to, set up a DynamoDB or S3 bucket with permissions. You can then run ‘serverless deploy’ from the project root and it’ll package everything up in a .serverless folder and upload to AWS, setting up a Cloudformation template and running it so you can then tear down the environment. It’s simple and really powerful. If you’re doing any work with Lambdas or AWS Functions, I’d recommend looking into serverless.
Below is an very simple yaml file for serverless. You can set the provider (serverless runs on Azure, AWS, IBM OpenWhisk currently), language version of your code. In environment, this would just read a yml file in the ‘vars’ folder depending on the stage. You can also run
To change the file being used from “dev” - which is set in the stage setting to “testing”. You can exclude files from being packaged up and if you have multiple Lambda functions, you can choose to package them up individually.
At the bottom of the yaml there is an API Gateway endpoint pointing to the Lambda function.
You can even run the Lambda function locally by using invoke local
. This is useful for local development.
Serverless is a great, powerful way to quickly deploy Lambda based services (or Functions if using Azure) and the best part is, it’ll work with your current system just by adding a yaml file. In this short blog post I’ve given a quick example of how to deploy a simple Lambda & API Gateway endpoint. You can also set up a Dynamo DB instance and many other services in the yaml file.