Announcement: Updated default retry behavior (2026) #3416

This issue tracks the 2026 retry updates for AWS SDK for Go 2.x. See the announcement blog post for the full story across all AWS SDKs, including how to tell if you are affected.

Status

What changed

When you set AWS_NEW_RETRIES_2026=true, the retry defaults within standard mode update. The retry mode itself does not change.

If you have explicitly configured max attempts or backoff, your value takes precedence for that setting.

DynamoDB defaults use a shorter base delay to match its low-latency profile. The additional attempt keeps the last retry's maximum backoff comparable to the general default.

Transient errors (such as 500s and connection resets) now use a much shorter backoff than throttling errors (where the service asks you to slow down). For details on backoff timing, error classification, and the retry quota, see Retry behavior in the AWS SDKs. For retry mode selection and configuration options, see Retry behavior in the AWS SDKs.

How to opt in

Once the release ships (we will update this issue), set the environment variable:

export AWS_NEW_RETRIES_2026=true

How to revert

During the opt-in period, remove the environment variable:

unset AWS_NEW_RETRIES_2026

After the default rollout (no sooner than November 2026), the AWS_NEW_RETRIES_2026 flag will be removed. A full revert to the previous behavior is not available because this SDK does not support legacy retry mode. You can override some individual settings:

import (
	"context"

	"github.com/aws/aws-sdk-go-v2/aws"
	"github.com/aws/aws-sdk-go-v2/aws/retry"
	"github.com/aws/aws-sdk-go-v2/config"
	"github.com/aws/aws-sdk-go-v2/service/dynamodb"
)

cfg, err := config.LoadDefaultConfig(context.TODO(), config.WithRetryer(func() aws.Retryer {
	return retry.AddWithMaxAttempts(retry.NewStandard(), 3)
}))
if err != nil {
	// handle error
}

client := dynamodb.NewFromConfig(cfg)

// if you want to override other fields per service
dynamoClient := dynamodb.NewFromConfig(cfg, func(o *dynamodb.Options) {
    o.Retryer = retry.NewStandard(func(so *retry.StandardOptions) {
        so.BaseDelay = 25 * time.Millisecond
        so.ThrottlingRetryCost = 5
        so.RetryCost = 14
    })
})

If full revert is a concern for your use case, please let us know in this issue.

Where you might notice a difference

For most workloads, the change is invisible or strictly better. Transient errors recover faster because the base delay is significantly shorter.

• Retry quota activates sooner for transient errors. Each transient retry costs 14 tokens (previously 5 for most errors). During sustained transient failures (such as 500s and connection resets), the retry quota triggers at a lower failure rate than the previous version of standard mode. Throttling retries cost 5 tokens.
• Long-polling operations now back off when the retry quota is depleted. Operations like SQS.ReceiveMessage apply a backoff delay before returning an error, even when retries are blocked. Without this, polling loops tighten during outages, spiking client CPU usage and generating additional load that can delay recovery. For details, see long-polling operations.

Overriding specific settings

You do not have to accept all changes as a bundle. If you opt in but want to keep a specific previous value, set it explicitly. Precedence applies per setting.

For example, to use the new backoff timing but keep a higher DynamoDB max attempts:

import (
	"context"

	"github.com/aws/aws-sdk-go-v2/aws"
	"github.com/aws/aws-sdk-go-v2/aws/retry"
	"github.com/aws/aws-sdk-go-v2/config"
	"github.com/aws/aws-sdk-go-v2/service/dynamodb"
)

cfg, err := config.LoadDefaultConfig(context.TODO(), config.WithRetryer(func() aws.Retryer {
	return retry.AddWithMaxAttempts(retry.NewStandard(), 9)
}))
if err != nil {
	// handle error
}

client := dynamodb.NewFromConfig(cfg)

For the full list of configurable settings and their precedence, see Retry behavior in the AWS SDKs.

Feedback

If you encounter unexpected behavior or have questions, comment on this issue. Your feedback during the opt-in period directly shapes when and how we make this the default.