MIGRATION ISSUE: Undocumented change in the behaviour of S3 client region redirects

[andrejleitner]

Pre-Migration Checklist

• I've read the Migration Guide.
• I've reviewed the upgrading notes and major version differences mentioned in UPGRADING.md.
• I've checked AWS Forums and StackOverflow for similar migration issues.

Which JavaScript Runtime is this issue in?

Node.js (includes AWS Lambda)

AWS Lambda Usage

• Yes, my application is running on AWS Lambda.
• No, my application is not running on AWS Lambda.

Describe the Migration Issue

I didn't find the following mentioned in the migration guide or notes:

So we deliberately removed the follow-the-redirect feature in v3.

Source: #1807

Code Comparison

No response

Observed Differences/Errors

PermanentRedirect error with v3: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.

Additional Context

No response

[siddsriv]

We've added a section for S3 Global Client and the followRegionRedirects flag (v3 only) in our UPGRADING.md.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.