Lambda Cold Starts, Concurrency, Provisioned Concurrency and SnapStart

By Ravindra Bagale, trainer · LinkedIn · Last updated: 2 November 2026

1. Everyday example: morning stove vs lunch rush

Sofia in Sofia (EUR) runs a ticket API. At 03:00 the stall is dark — first invoke pays init. At 12:00 ten stoves stay warm. If a flash sale needs p99 under 200 ms, she may buy provisioned concurrency — like paying rent to keep one stove lit overnight. If traffic is sparse, she measures and skips the rent.

Basics: What Is AWS Lambda? and first Lambda. This chapter is the performance and concurrency pattern layer.

2. Why care?

Why do we need this?

Users feel cold starts as random slowness. Bursts hit account concurrency and throttle. Blindly buying provisioned concurrency burns budget in USD or INR. Architecture means measure, then choose.

What is it?

Cold start = create execution environment + init code. Warm = reuse env. Reserved concurrency = cap a function. Provisioned concurrency = keep N envs initialized (you pay). SnapStart (Java) = snapshot init to speed cold starts.

3. Vertical diagram

4. How: measure then decide

How to do it (step by step)

1. Turn on JSON logs or read REPORT Init Duration.
2. Separate p50 handler vs p99 with cold starts.
3. Check get-account-settings ConcurrentExecutions.
4. Set reserved concurrency on noisy neighbors.
5. Only if SLO needs it: provisioned concurrency or SnapStart.
6. Re-measure monthly — traffic shape changes.

5. Per-concept commands

Account concurrency settings

aws lambda get-account-settings --region ap-south-1 \
  --query 'AccountLimit' 

Meaning: Shows UnreservedConcurrentExecutions — your shared burst pool.

Function concurrency config

aws lambda get-function-concurrency --region ap-south-1 \
  --function-name ticket-api 

Meaning: Reserved limit if set; empty means use account pool.

Provisioned concurrency config

aws lambda get-provisioned-concurrency-config --region ap-south-1 \
  --function-name ticket-api --qualifier prod 

Meaning: Confirms allocated vs available; status READY before trusting latency.

Pull Init Duration from logs (insight query sketch)

aws logs filter-log-events --region ap-south-1 \
  --log-group-name /aws/lambda/ticket-api \
  --filter-pattern 'Init Duration' --limit 10 

Meaning: Cold starts leave Init Duration in REPORT — count them before buying provisioned.

6. Memory, CPU, package size

• More memory = more CPU on Lambda — sometimes faster and cheaper.
• Huge layers/deps extend cold start — trim package.
• VPC ENI attach historically hurt cold starts — understand Hyperplane era still has cost.
• Java: enable SnapStart on published versions; validate uniqueness of entropy.

7. When provisioned is worth it

8. Industries

• Fintech (Aisha, Lagos, NGN): authorize path provisioned; batch reports not.
• Ecommerce (Rohan, Pune, INR): checkout warm; recommendations async.
• Healthcare (Mei, Singapore, SGD): appointment book low latency.
• Media (Kenji, Osaka, JPY): thumbnail workers — cold OK.
• SaaS (Priya, Bengaluru, INR): multi-tenant API with reserved per tier.

9. Lab

10. Lab - measure cold starts

Do this in ap-south-1 (Mumbai) unless your org forbids it. Set a budget alert first.

How to do it (step by step)

1. Invoke a lab function once after 15+ min idle; note Init Duration.
2. Invoke 20 times quickly; note how many lack Init Duration.
3. Read get-account-settings; write the unreserved number.
4. Estimate monthly provisioned cost for N=2 at your memory size (USD and INR).

Cleanup (stop billing)

1. Delete provisioned configs you created for the lab.
2. Remove lab function if unused.

11. Same pattern across industries

• Fintech (Aisha, Lagos): payment webhooks → SQS → Lambda; never block the bank callback thread.
• Ecommerce (Rohan, Pune): checkout API on API Gateway+Lambda; inventory fan-out on SNS.
• Healthcare (Mei, Singapore): appointment SMS via SNS; PHI stays in DynamoDB with fine-grained IAM.
• EdTech (Diego, São Paulo): nightly cleanup EventBridge → Lambda on student drafts.
• Logistics (Fatima, Casablanca): package scan events on EventBridge bus; Step Functions for customs saga.
• Media (Kenji, Osaka): S3 upload → Lambda thumbnails; fan-out to moderation + CDN invalidate.
• SaaS multi-tenant (Priya, Bengaluru): Cognito groups + DynamoDB partition per tenant.
• Gov portal (Omar, Amman): strangler fig — peel one PDF form route per sprint to Lambda.

12. Troubleshooting checklist

1. Confirm region (ap-south-1 vs us-east-1 for CloudFront/ACM quirks).
2. Check CloudWatch Logs for the function name and request id.
3. Verify IAM execution role allows the API you call.
4. For async: check DLQ depth and SQS age of oldest message.
5. For APIs: curl -v and compare status, CORS headers, body.
6. For workflows: open Step Functions execution event history.
7. Re-read the linked deep chapter before reinventing a service.
8. If cost spikes: check concurrency, retries, and provisioned capacity.

13. Common errors and fixes

Each row is a real mistake students and juniors hit. Read the fix before you panic.

14. FAQ

15. Interview Q&A (Beginner / Mid / Senior + MNC)

16. Tips in English, Marathi and Hindi

17. Architecture decision checklist

1. Write the user journey in five bullets with no AWS names.
2. Mark each step sync (user waits) or async.
3. Name failure mode: retry, DLQ, compensate, or alert-only.
4. Name the idempotency key for every write.
5. Pick data store from access patterns (link DynamoDB modeling).
6. Estimate monthly cost at 1x and 10x traffic (USD and INR).
7. Confirm account concurrency and service quotas in ap-south-1.
8. Decide auth: Cognito, IAM, Lambda authorizer, or none.
9. Name on-call and which CloudWatch alarm pages them.
10. Link the deep chapter you will not rewrite.
11. Only then open console or IaC.

18. Copy-paste quick commands (read-only first)

# Region and identity
aws configure get region
aws sts get-caller-identity

# Lambda landscape
aws lambda list-functions --region ap-south-1 --max-items 20 \
  --query 'Functions[].{N:FunctionName,R:Runtime,T:Timeout,M:MemorySize}' --output table
aws lambda get-account-settings --region ap-south-1

# API Gateway (HTTP APIs)
aws apigatewayv2 get-apis --region ap-south-1 --query 'Items[].{N:Name,Id:ApiId,Ep:ProtocolType}' --output table

# Queues and topics
aws sqs list-queues --region ap-south-1
aws sns list-topics --region ap-south-1 --query 'Topics[].TopicArn'

# Event buses and state machines
aws events list-event-buses --region ap-south-1
aws stepfunctions list-state-machines --region ap-south-1 --query 'stateMachines[].name'

# DynamoDB tables (names only)
aws dynamodb list-tables --region ap-south-1

Run these in a sandbox account. Prefer read-only IAM while learning.

19. More industry and stack stories

• Fintech (Aisha, Lagos, NGN): bank webhooks must return 200 fast — SQS absorbs spikes; ledger Lambda is idempotent on paymentId.
• Ecommerce (Rohan, Pune, INR): Black Friday — API Gateway throttle + SQS order intake; SNS fans inventory, email, analytics.
• Healthcare (Mei, Singapore, SGD): appointment reminders via SNS SMS; PHI only in DynamoDB with condition keys.
• EdTech (Diego, São Paulo, BRL): EventBridge nightly cleanup of draft quizzes; Lambda timeout 30s, not 15 min.
• Logistics (Fatima, Casablanca, MAD): package scans on custom EventBridge bus; Step Functions customs saga.
• Media (Kenji, Osaka, JPY): S3 → Lambda thumbnails; never write thumbs to the watched prefix.
• SaaS (Priya, Bengaluru, INR): Cognito groups + DynamoDB PK tenantId; one Lambda authorizer for all routes.
• Gov (Omar, Amman, JOD): strangler — peel one PDF form route per sprint from the monolith.
• Startup (Sofia, Sofia, EUR): start with Function URL for demos; move to HTTP API when partners need JWT.
• Retail (Luis, Mexico City, MXN): store POS sync via SQS FIFO when order matters; Standard when it does not.

• Python: handlers thin; put domain logic in plain modules for unit tests without Lambda.
• Node: prefer async/await; never block the event loop on sync DNS.
• Java: SnapStart for cold starts; keep dependencies lean.
• .NET: AspNetCoreServer for low-traffic tenants; watch package size.
• Go: single static binary; great for SQS workers.
• PHP: keep Laravel queues on ECS; Lambda for S3/webhooks glue.

20. Glossary (short)

21. Practice: explain out loud

1. 60 seconds: everyday story for Lambda cold starts and concurrency.
2. 60 seconds: sync vs async with a checkout example.
3. 60 seconds: when you refuse Lambda.
4. 60 seconds: DLQ + idempotency in one breath.
5. Record once; cut fillers; record again.

22. Safe lab hygiene

• Tag every lab resource with owner and expiry date.
• Set a monthly AWS Budget alarm in INR or USD before experiments.
• Prefer read-only commands first; mutate in a sandbox account.
• Delete queues, APIs, tables you created — DynamoDB and APIGW leave footprints.
• Never put production secrets in env vars or screenshots.
• Do not enable provisioned concurrency for a hello-world.

23. How this chapter links others

• Compute depth: Lambda.
• HTTP edge: API Gateway.
• Data modeling: DynamoDB.
• Messaging: SQS/SNS.
• Events: EventBridge.
• Workflows: Step Functions.
• Project chapters (build-*): worked assemblies — link, do not paste.

24. Myths to drop

25. Error budget thinking for serverless

If your monthly error budget is 0.1% on checkout, a fan-out that retries aggressively can burn the budget with duplicate emails while money stays correct. Separate business correctness SLOs from notification SLOs.

1. Write two SLOs: money-correct and notify-delivered.
2. Retries on money path: bounded + idempotent.
3. Retries on notify path: best-effort + DLQ.
4. Page humans on money DLQ; ticket on notify DLQ.

26. Regional notes (ap-south-1)

• Build labs in Mumbai (ap-south-1) unless your org mandates elsewhere.
• Some services launch first in us-east-1 — check feature availability.
• Data residency for INR fintech may require in-region only.
• Latency to end users in India usually favors ap-south-1.

27. Naming conventions that save incidents

# Suggested prefixes
# Lambda:  pay-intake-prod, pay-worker-prod
# SQS:     pay-orders.fifo / pay-orders-dlq
# SNS:     pay-order-events
# EB bus:  pay.domain
# SFN:     pay-refund-saga
# DDB:     pay-orders-prod

Include env (dev/stage/prod) and domain. Future you grepping CloudWatch will thank present you.

28. Pre-mortems (ten minutes)

1. Imagine tomorrow headline: double charge in AED. What broke?
2. Imagine DLQ depth 50,000 after a bad deploy. How do you drain?
3. Imagine Cognito outage. Do APIs fail closed or serve read-only?
4. Write answers in the runbook before go-live.

29. Currency and locale in examples

Rotate currencies in designs: INR, USD, EUR, AED, NGN, BRL, JPY, SGD. Rotate names: Aisha, Rohan, Mei, Diego, Fatima, Kenji, Priya, Omar, Sofia, Luis. This keeps mental models global — not one-country samples.

30. Worked story: Rohan flash sale (INR)

1. Checkout Lambda p99 1.8s from cold starts.
2. Measured 40% invokes cold in first 2 minutes.
3. Provisioned=5 on alias live; p99 220ms.
4. Async email worker left on-demand.

31. Anti-patterns

• Provisioned on every function including cron.
• Ignoring account ceiling during load tests.
• Tuning without REPORT metrics.

Revision, interview and comparison cards

Revise this lesson in a few minutes. Save the cards on your phone or download them as PNG files. The QR code on each card opens this lesson.

More cards: Ravi Sir's Cards.