ST-2026-011 · SDKs, clients & toolchains
AWS will standardise SDK retry defaults across languages in November 2026
AWS introduced opt-in retry behavior with consistent standard and adaptive defaults across SDKs and tools and says the new behavior will become the default in November 2026, changing retry quotas, backoff timing and some maximum-attempt behavior.
Previous state
Retry defaults varied between AWS SDKs; several language SDKs and the AWS CLI defaulted to legacy behavior without the standard retry quota.
Current state
Supported SDKs can opt in now, and AWS plans to make consistent standard/adaptive retry behavior the default in November 2026, including revised token costs, error-specific backoff and lower retry counts in some clients.
Affected users
Who needs to care
Application teams using AWS SDKs, the AWS CLI or AWS Tools for PowerShell without fully explicit retry configuration, especially Java, Python, Ruby, PHP, C++ and CLI workloads that defaulted to legacy mode.
Required response
What to do
Identify SDK and tool versions, opt in with AWS_NEW_RETRIES_2026 in non-production, test failure latency and retry-dependent workflows, set explicit max-attempt or retry-mode overrides where required, and deploy supported versions before the default rollout.
Evidence boundary
What the source does not prove
AWS gives November 2026 as the default-rollout month but does not state an exact day. Explicit legacy-mode configurations remain unchanged, and opt-in availability differs by SDK version and language.
Lifecycle history
Dated event sequence
- Opt-in period opened
AWS published the cross-SDK behavior and enabled the AWS_NEW_RETRIES_2026 flag in supported releases.
- Default rollout planned
AWS plans to apply the updated retry defaults automatically during November 2026.
Evidence ledger
First-party sources
- 01AWS Developer Tools Blog — Announcing updated retry behavior for AWS SDKs and Tools
Official cross-SDK behavior announcement · 2026-05-20
Open official source ↗