SDK Rules

The cost, security, and reliability failure modes that AWS SDK rules exist to prevent, and why an SDK call is riskier than a plain function call.

The shortest path to the enumerated AWS SDK rule references, plus the five habits to adopt first before reading any checklist.

Twenty checkbox rules for never hardcoding or leaking AWS credentials: use the default chain, prefer roles, rotate keys, and keep secrets out of code and logs.

Checkbox rules for catching specific AWS errors, retrying only idempotent operations with bounded backoff, and logging the request id on every failure.

Enumerated rules for closing SDK clients, releasing connections and streams, and tearing down AWS resources so nothing is left orphaned and billing.

The cross-cutting index of the SDK Rules section: one condensed best-practice per category, each linking to the full checklist for credentials, errors, cost, cleanup, and security.