//
Busca en todas las páginas de la documentación
8 pages in this section.
Why every AWS SDK for JavaScript v3 call is `client.send(new XCommand(input))` instead of a method, and what that design buys you in bundle size and middleware.
An intro tour of the AWS SDK for JavaScript v3: install a per-service client, send your first command, read the response, handle typed errors, and paginate.
Why the AWS SDK for JavaScript v3 ships one `@aws-sdk/client-<service>` package per service, and what that means for node_modules, bundlers, and Lambda cold starts.
How the AWS SDK for JavaScript v3 exposes credential resolution as explicit, composable functions from @aws-sdk/credential-providers, and when to reach for each one.
How to import and run the AWS SDK for JavaScript v3 from Deno and Bun, using npm: specifiers and node_modules, plus the credential and permission gotchas each runtime brings.
The AWS SDK for JavaScript v3 habits to internalize first: import hygiene and tree-shaking, per-service client reuse, typed command inputs and errors, credentials, and bundle-aware config.