Uses AWS Lambda, SQS and the Serverless Framework. A Consumer receives messages from SQS with a payload which it POST's to a callback URL. If the callback POST fails then the message is requeued with an exponential back-off delay.
The Serverless Framework is used to deploy the application to AWS Lambda. A local version is installed as a dev dependency using NPM. Follow the Serverless AWS credentials setup guide to ensure access to AWS is configured correctly.
The serverless.yaml file needs to know your 12 digit [AWS Account ID] (https://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html#FindingYourAWSId).
The POST callback uses a custom headers which can be prefixed with your project or service name. Just edit the .env file and change HEADER_NAME
A deployment bucket centralizes all your Serverless deployments in to a single bucket in S3 rather than creating a new bucket for each Serverless project and each environment. Make sure the bucket exists, create it if it does not. The deployment will append the region to the bucket prefix. Edit the .env file and change DEPLOY_BUCKET_PREFIX.