A synchronous API uses Lambda and must avoid initialization delay on the first request.
Keep a number of execution environments initialized in advance.
Which feature is most appropriate?
Configure Lambda Provisioned Concurrency to keep initialized execution environments available for synchronous requests.
Detailed explanation
S3 Lifecycle manages objects and does not cache Lambda execution environments.
S3 Lifecycle manages objects and does not cache Lambda execution environments.
A shorter timeout does not prepare an initialized execution environment.
A shorter timeout does not prepare an initialized execution environment.
DNS caching does not skip Lambda initialization.
DNS caching does not skip Lambda initialization.
Provisioned Concurrency prepares initialized execution environments and reduces cold-start latency.
Provisioned Concurrency prepares initialized execution environments and reduces cold-start latency.
Check official documentation
Compare the following points with the official documentation.
AWS Lambda Provisioned Concurrencyの公式説明を確認する。
What to confirm
コールドスタート対策をProvisioned Concurrencyへ対応付けられる。
Key points
- Provisioned Concurrency
- Cold start
- Lambda
Notes
- Environment: AWS公式Lambdaドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Initialization versus timeout
A timeout limits execution duration; it does not remove initialization latency.
Synchronous experience
Provisioned environments are useful when request latency must remain predictable.