Microservices implemented using Serverless. Click into a specific microservice directory for additional instructions
- When using the Serverless CLI, specify
--aws-profile <profile-name>to apply the correct permissions- AWS CLI profiles are stored in
~/.aws/credentials - Currently, the IAM user designed for use with Serverless is
sls - Currently, Serverless does not have a complete list of IAM permissions required
- AWS CLI profiles are stored in
- As recommended by Serverless, environment variables stored in AWS Parameter Store (within AWS Systems Manager)
- Currently, we use IAM to manage externally-issued SSL certificates
- AWS ACM is the recommended certificate manager so IAM-managed certificates can only be accessed via the AWS CLI (no console access)
- Note that our IAM-managed certificates have paths prefixed with
/cloudfrontin order to be usable with Cloudfront as required in the docs - Because Serverless uses CloudFormation to deploy, only ACM-managed certificates are supported
- AWS Lambda execution context is reused for a period of time, so keep expensive initializations outside of the export body
- AWS lambda configuration limits
- AWS API Gateway lambda vs lambda proxy integration
- Overview of Serverless
- Axios request library documentation
- Intro to ES2015 classes
serverless-api-cloudfrontdocumentation- Serverless testing guide
- Serverless AWS Lambda CLI reference
- Serverless guide to handling CORS