The retry request of PutBucket will behave differently between regions.

[rmt2021]

Describe the bug

For instance, if a PutBucket succeeds in the remote but then transient network errors happen, a transient error code may be returned (e.g., 503) to the client. So the SDK retry mechanism will retry the same PutBucket operation again (send another retry request whose "amz-sdk-request" header value would be "attempt=2; max=5").

However, we noticed that the retry request would behave differently when sent to different regions.

• If the retry request of PutBucket is sent to us-east-1, the response will be 200 OK. (idempotent behavior)
• However, if the retry request of PutBucket is sent to us-east-2, the response will be 409 with "Your previous request to create the named bucket succeeded and you already own it". (Non-idempotent behavior)

Expected Behavior

The behavior of the retry request should be consistent.

Current Behavior

If I use the us-east-1, the retry request of PutBucket will be idempotent.
If I use the us-east-2, the retry request of PutBucket will be non-idempotent.

Reproduction Steps

One way to reproduce is to trigger a retry request by changing the status code to retriable error codes (e.g., 503).

Possible Solution

No response

Additional Information/Context

Is this an erroneous server-side behavior?

AWS .NET SDK and/or Package version used

AWSSDK.S3 3.7.9.31

Targeted .NET Platform

.NET 6

Operating System and version

Windows 10 Pro

[ashishdhingra]

@rmt2021 Thanks for reporting the scenario. The possible for different behavior in us-east-1 region is due to legacy reasons and maintaining backward compatibility. We have seen similar issue in the past in other SDK(s) where similar behavior was observed. Please refer S3: Error Responses for more details where for error code BucketAlreadyOwnedByYou it mentions that The bucket that you tried to create already exists, and you own it. Amazon S3 returns this error in all AWS Regions except in the US East (N. Virginia) Region (us-east-1). For legacy compatibility, if you re-create an existing bucket that you already own in us-east-1, Amazon S3 returns 200 OK and resets the bucket access control lists (ACLs).. Hope this helps.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.