-
Notifications
You must be signed in to change notification settings - Fork 1k
New pattern submission: sqs to lambda managed instance with provisioned mode esm #3002
Description
Amazon SQS + Lambda Managed Instances (LMI) with Provisioned Mode ESM
This pattern deploys an Amazon SQS Standard Queue connected to an AWS Lambda function via an Event Source Mapping (ESM) configured with Provisioned Mode — an ESM feature that pre-allocates dedicated polling resources for predictable, high-throughput message processing.
Learn more about this pattern at Serverless Land Patterns: https://serverlessland.com/patterns/sqs-lambda-lmi-esm-provisioned-sam
Important: this application uses various AWS services and there are costs associated with these services after the Free Tier usage - please see the AWS Pricing page for details. You are responsible for any AWS costs incurred. No warranty is implied in this example.
Requirements
- Create an AWS account if you do not already have one and log in. The IAM user that you use must have sufficient permissions to make necessary AWS service calls and manage AWS resources.
- AWS CLI installed and configured
- Git Installed
- AWS Serverless Application Model (AWS SAM) installed
Build Instructions
- From the command line, use AWS SAM to build the AWS resources for the pattern as specified in the template.yml file:
sam build
Deployment Instructions
-
Create a new directory, navigate to that directory in a terminal and clone the GitHub repository:
git clone https://github.com/aws-samples/serverless-patterns -
Change directory to the pattern directory:
cd sqs-lambda-lmi-esm-provisioned-sam -
From the command line, use AWS SAM to deploy the AWS resources for the pattern as specified in the template.yml file:
sam deploy --guided -
During the prompts:
- Enter a stack name
- Enter the desired AWS Region
- Accept the default parameter values or tune them for your workload
- Allow SAM CLI to create IAM roles with the required permissions.
Once you have run
sam deploy --guidedmode once and saved arguments to a configuration file (samconfig.toml), you can usesam deployin future to use these defaults. -
Note the outputs from the SAM deployment process. These contain the resource names and/or ARNs which are used for testing.
How it works
- A producer (any AWS service, SDK client, or CLI) sends messages to the SQS Standard Queue.
- The ESM's provisioned event pollers continuously long-poll the queue using up to 10 SQS API calls per second per poller.
- When messages are available, pollers assemble batches (up to
BatchSizemessages, waiting up toMaxBatchingWindowInSeconds) and invoke the Lambda function concurrently. - Lambda scales the number of active pollers between
MinimumPollersandMaximumPollersbased on queue depth, adding up to 1,000 concurrent executions per minute. - If a message fails processing after 3 attempts (
maxReceiveCount), it is moved to the Dead Letter Queue. - A CloudWatch Alarm fires as soon as any message lands in the DLQ.
Testing
- Get the queue URL from the stack outputs:
aws cloudformation describe-stacks \
--stack-name <your-stack-name> \
--query "Stacks[0].Outputs"- Send test messages:
QUEUE_URL=<QueueUrl from outputs>
# Send a single message
aws sqs send-message \
--queue-url $QUEUE_URL \
--message-body '{"orderId": "123", "amount": 99.99}'
# Send a batch of 10
for i in $(seq 1 10); do
aws sqs send-message \
--queue-url $QUEUE_URL \
--message-body "{\"orderId\": \"$i\", \"amount\": $((RANDOM % 100))}"
done- Check Lambda logs:
sam logs --stack-name <your-stack-name> --tail- Inspect the ESM status and poller count:
ESM_ID=<EventSourceMappingId from outputs>
aws lambda get-event-source-mapping --uuid $ESM_IDCleanup
- Delete the stack
aws cloudformation delete-stack --stack-name STACK_NAME
- Confirm the stack has been deleted
aws cloudformation list-stacks --query "StackSummaries[?contains(StackName,'STACK_NAME')].StackStatus"
Copyright 2025 Amazon.com, Inc. or its affiliates. All Rights Reserved.
SPDX-License-Identifier: MIT-0