//
Search across all documentation pages
7 pages in this section.
How an AWS SDK client turns a service name and region into a concrete endpoint, why region is mandatory, and how client construction wires it together.
Hands-on basics for SDK mechanics: build a client with an explicit region, inspect the resolved endpoint, attach config, and read request metadata in both SDKs.
Build one client per region and route between them for latency and disaster recovery, using a small cache so clients are reused rather than rebuilt per call.
Set connect and read/socket timeouts and tune the HTTP connection pool in boto3 (Config) and AWS SDK v3 (NodeHttpHandler) so slow calls fail fast and scale.
The SDK-mechanics habits that avoid per-request overhead: reuse clients, pin region, set explicit timeouts and pool size, prefer resolution over hardcoded endpoints.