//
Busca en todas las páginas de la documentación
8 pages in this section.
The client-request-response mental model shared by every AWS SDK, and how it builds, signs, and sends HTTPS calls differently from the Console, CLI, and IaC.
An intro tour of the AWS SDK: install a client, make your first call, read the response, handle errors, and paginate, in both Python (boto3) and TypeScript (SDK v3).
The four surfaces onto the same AWS API - Console, CLI, SDK, and IaC - when to reach for each, and how they compose in a real team workflow.
How AWS charges for SDK calls: per-request pricing, data transfer, free-tier gotchas, and how loops, polling, and pagination can quietly run up a bill.
How every AWS SDK call becomes a signed HTTPS request: the endpoint, headers, SigV4 signature, request id, and how boto3 and SDK v3 build it under the hood.
How to map an AWS REST API reference operation to its boto3 method and AWS SDK for JavaScript v3 command, including parameter casing, shapes, errors, and pagination.
The core AWS SDK habits to internalize first: credential hygiene, client reuse, error and retry handling, pagination, region and endpoint config, and cost control.