What problem does it solve? Writing correct JavaScript or TypeScript code against AWS services with the v3 SDK involves many non-obvious pitfalls: unread streams causing socket exhaustion, mutating resolved client config, wrong credential providers, and streaming deadlocks under parallel load. This Skill provides verified patterns and reference material so generated code follows the SDK's intended usage. ## Core Features & Use Cases - Client and Credential Patterns: Covers bare-bones vs aggregated clients, per-client configuration, all credential providers from @aws-sdk/credential-providers (AssumeRole, SSO, web identity, Cognito), and sharing credentials across regions. - Service-Specific Guidance: Includes DynamoDB DocumentClient marshalling, S3 presigned URLs, multipart uploads, waiters, paginators, middleware, abort controllers, and SigV4a for Multi-Region Access Points. - Operational Best Practices: Documents Lambda initialization patterns, Node.js version requirements, TypeScript typing helpers, error handling with $metadata, and performance tuning for parallel workloads. - Use Case: When asked to write a Lambda function that uploads files to S3 and records metadata in DynamoDB, this Skill ensures the code initializes clients outside the handler, uses lib-storage for multipart upload, and uses lib-dynamodb for native JS types. ## Quick Start Write a Node.js script using the AWS SDK v3 that downloads an object from S3 and handles errors correctly.
