Architecture note2 lab guides2 lab guides
Lambda · Serverless Functions
Execution model, cold starts, concurrency accounting, and the throttle storms that take down everything sharing your account limit.
Outcome
- Create a Lambda execution role with least-privilege permissions
- Deploy a function via CLI zip upload
- Invoke synchronously and asynchronously and explain the difference
- Read the
REPORTline in CloudWatch Logs and identify cold start duration - Update function code and wait for propagation
- Explain why Lambda has one role (vs ECS's two)
- Add an inline IAM policy and invoke without redeploying
- Fetch a Secrets Manager secret at module level (cached per environment)
- Diagnose an
AccessDeniederror and identify which permission is missing
- Create an HTTP API Gateway and wire it to a Lambda function
- Return a valid API Gateway response shape from the handler
- Create an SQS event source mapping with a DLQ
- Explain what happens when Lambda throws on an SQS batch (retry + DLQ)
- Set reserved concurrency and explain the dual guarantee/cap semantics
- Publish a version and create an alias
- Configure a weighted alias for a canary deploy
- Set concurrency to 0 and understand when you'd use this
- Write a Logs Insights query to get P99 duration and cold start rate
- Enable X-Ray active tracing and
patch_all()for boto3 - Read a trace and identify which sub-segment has the most latency
- Name the six default Lambda CloudWatch metrics and what each measures