Lambda

How Lambda's execution environments, cold starts, and concurrency model shape what you do from an SDK - the split between the control plane that manages a function and the data plane that invokes it.

Update a function's code and configuration, then invoke it synchronously and asynchronously in both Python (boto3) and TypeScript (AWS SDK v3), including reading the response payload and tail logs.

Publish a Lambda layer and attach it to functions from boto3 and AWS SDK v3 to share code and dependencies, including layer versioning, compatible-runtime filters, and the five-layer limit.

Configure provisioned concurrency for latency-sensitive Lambda functions from boto3 and AWS SDK v3 - pre-warming execution environments on a version or alias, checking readiness, and separating it from reserved concurrency.

Create and configure Lambda Function URLs from boto3 and AWS SDK v3, choosing AWS_IAM vs NONE auth, adding the resource-based permission a public URL needs, and contrasting URL calls with the Invoke API.

Defaults every Lambda-via-SDK integration should set explicitly: deployment package hygiene, timeout/memory tuning, safe deploys with versions and aliases, trigger tuning, and observability across boto3 and AWS SDK v3.