Caching in AWS Lambda
This repository presents three different ways to use caching in AWS Lambda functions. You can use this to start with your own caching setup by using one of the following approaches:
- Simple Caching: you only cache data within a Lambda function. This makes sense if you your cached data will not change frequently. The disadvantage is that no cache synchronization happens between the instances of your Lambda functions and their local caches.
- Custom Caching: you are deploying your own caching service. Since you don't want to put your cached data to a public EC2 instance, you'll keep your cache instances in a VPC. Unfortunately this requires you to also put your Lambda functions into the same VPC in order to let them access the cache. In this example I'm using a Java Lambda function which is connecting to Hazelcast on an EC2 instance.
- Managed Caching: you are using ElastiCache which is a managed caching service by AWS. The setup is the same as in the Custom Caching example. You can choose between Redis and Memcached here. The example is based on a NodeJS Lambda connecting to a Redis cluster.
Each folder contains a
deploy.sh file which lets you easily deploy the related CloudFormation template.
You only need to provide a
LAMBDA_BUCKET environment variable pointing to an S3 bucket where the Lambda function artifacts are uploaded to (necessary for deployment).
Copyright (c) 2018 Sebastian Hesse
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.