What problem does it solve? Writing AWS code often leads to hardcoded credentials, overly permissive IAM policies, DynamoDB scans that blow up costs, and SQS consumers that duplicate or lose messages. This Skill provides production-grade patterns for boto3 and AWS SDK v3 that prevent credential leaks, throttling failures, and audit findings. ## Core Features & Use Cases - Credential Chain & IAM Least Privilege: Enforces role-based authentication (instance profiles, OIDC for GitHub Actions, Lambda execution roles) and provides scoped IAM policy templates with specific actions and resource ARNs. - Service Patterns for S3, DynamoDB, Lambda, SQS: Covers presigned URLs, multipart uploads, single-table DynamoDB design, warm-instance client reuse in Lambda handlers, and SQS partial batch failure handling. - Secrets, Retries, and Cost Controls: Includes Secrets Manager vs Parameter Store guidance, botocore adaptive retry configuration, ClientError branching by error code, and cost levers like S3 lifecycle policies. - Use Case: You are writing a Lambda function triggered by SQS that reads from DynamoDB and writes to S3. Activate this Skill to get the correct handler structure, visibility timeout guidance, batchItemFailures response format, and a least-privilege IAM policy. ## Quick Start Ask the AI to write a Lambda handler that processes SQS messages with partial batch failure support and least-privilege IAM permissions.