How does Lambda@Edge scaling work?

How does Lambda@Edge handle scaling when traffic increases? Is it automatic, or do I need to configure anything?

What are the limitations on Lambda@Edge scaling? Are there quotas or limits I should be aware of?

When dealing with critical functions, is there a way to ensure they have enough resources? Are there different ways to configure concurrency for Lambda@Edge functions?

Topics

Networking & Content Delivery

Tags

Amazon CloudFront Lambda@Edge

Language

English

Piotrek

asked 4 months ago178 views

1 Answer

Newest
Most votes
Most comments

Accepted Answer

Lambda@Edge capacity scales dynamically in response to increased traffic. It depends on the available concurrency of AWS Lambda in your account and AWS regions. While the concept of a region doesn’t apply to Lambda@Edge functions, regional AWS Lambda quotas correspond with Lambda@Edge scaling in Regional Edge Caches. The following quotas apply:

for requests per second, per region, per function
for concurrent executions per region, across all functions in each AWS account

These quotas can be increased by requesting a service quota increase. Additionally, the following quotas apply:

for additional execution environments provisioned every 10 seconds, per region, per function
for requests per second, per execution environment, even if the function execution takes less than 100ms

For more information, see Function scaling in the AWS Lambda Developer Guide. Please note that reserved concurrency and provisioned concurrency can not be enabled/applied for Lambda@Edge functions.