Default Timeout and Retry Configuration #4466
rcoh
announced in
Change Log
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Prior to the upcoming BehaviorMajorVersion, if a Rust SDK or smithy client was NOT instantiated using
aws_config::load_from_envas baseline configuration, then it would NOT have a default "Connection Timeout" and would default to no retries.This directly contrasts with the documented behavior. The new behavior version,
BehaviorVersion::v2026_01_12(), will enable connection timeouts and retries automatically regardless of how the client was constructed. If you are currently usingBehaviorVersionLatest, you will be opted into this automatically.Recommendations
operation_timeouts,operation_attempt_timeouts, andconnect_timeouts.BehaviorVersion::latestto ensure you are aware of all changes in SDK behavior.Code Examples
When a client is instantiated directly via
from_confand the config builder was NOT instantiated viaconfig::Builder::from(&sdk_config), the retry and timeout settings will not be set:If you are using
Client::from_conf, to manually set timeouts, use this pattern:Beta Was this translation helpful? Give feedback.
All reactions