aws-sdk-js-v3-usage

What problem does it solve?

AWS SDK for JavaScript v3 has many subtle differences from v2 (client instantiation, streaming behavior, credentials, pagination, and configuration), and getting them wrong can cause runtime bugs, socket exhaustion, or incorrect request behavior.

Core Features & Use Cases

• Correct imports and client styles: Use service-specific clients from @aws-sdk/client-* with the preferred “bare-bones” pattern, or the aggregated v2-style API when appropriate.
• Safe client configuration: Set region explicitly (or via AWS_REGION), use retry configuration correctly, and avoid reading or mutating client.config after instantiation.
• Production-grade handling for real workloads: Read or discard streaming responses properly, use paginator helpers instead of manual tokens, and implement robust error handling patterns.

Use case: You are migrating a Node.js/TypeScript AWS integration to SDK v3 and need consistent patterns for credentials, streaming S3 GetObject bodies, paginated DynamoDB reads, and service error handling.

Quick Start

Tell the assistant: "Show me the correct AWS SDK for JavaScript v3 pattern to create an S3 client, fetch an object safely as a stream, and handle service errors."