Error: dynamodb unable to execute http request

“Unable to execute HTTP request” is a Java SDK transport error. The nested cause identifies whether DNS resolution, connection setup, TLS, a socket read, or connection-pool acquisition failed. It is not enough by itself to diagnose IAM permissions or a DynamoDB outage.

• UnknownHostException or connection refusal: verify the endpoint hostname, Region, local listener, and network route.
• TLS or certificate errors: verify the hostname and JVM trust store, including any approved corporate proxy CA. Do not disable certificate validation.
• Connection or read timeouts: compare network behavior with the configured connection, socket, API-attempt, and total-call timeouts.
• Pool acquisition timeout: inspect client HTTP metrics and concurrency. Reuse clients and avoid closing a shared client while requests are still using it.

Use the current AWS SDK for Java 2.x. Preserve the full exception chain and request metadata where available. A received AccessDeniedException is a service response and requires a different investigation. A transport failure after sending a write can leave its outcome unknown, so reconcile before repeating a non-idempotent update.

See Java SDK examples and AWS documentation.