Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please update presigned URL documentation #2864

Closed
Basil-P opened this issue May 12, 2021 · 6 comments
Closed

Please update presigned URL documentation #2864

Basil-P opened this issue May 12, 2021 · 6 comments
Assignees
Labels
documentation This is a problem with documentation. feature-request This issue requests a feature.

Comments

@Basil-P
Copy link

Basil-P commented May 12, 2021

Please could you amend the Boto3 documentation regarding Presigned URL's. The documentation does not mention the problem raised by issue #2728 - Uploading files using presigned url in af-south-1 #2728

The existing documentation relating to Presigned URL does not mention the addition of endpoint_url="" for any region launched after March 20, 2019 such as af-south-1.

eg.. s3_client = boto3.client('s3', region_name='af-south-1', endpoint_url='https://s3.af-south-1.amazonaws.com')
Not specifying this parameter will continue to generate the "IllegalLocationConstraintException" error. We are using the latest version of boto3-1.17.71 botocore-1.20.71

In issue #2728 https://github.com/swetashre mentions the solution and reasoning for this.

For all Regions that launched after March 20, 2019, if a request arrives at the wrong Amazon S3 location, Amazon S3 returns an HTTP 400 Bad Request error. Basically this means s3 region re-director won't work for region launched after march 20, 2019. That's why when you are specifying the exact endpoint_url it works. I hope it helps. Please let me know if you have any more questions.

https://boto3.amazonaws.com/v1/documentation/api/latest/guide/s3-presigned-urls.html

I've lost 3 days of my life with this issue :-)

@Basil-P Basil-P added guidance Question that needs advice or information. needs-triage This issue or PR still needs to be triaged. labels May 12, 2021
@kdaily kdaily added documentation This is a problem with documentation. feature-request This issue requests a feature. and removed guidance Question that needs advice or information. needs-triage This issue or PR still needs to be triaged. labels May 14, 2021
@kdaily
Copy link
Member

kdaily commented May 14, 2021

Hi @Basil-P, thanks for bringing this up. I'll review this with the docs writers.

@Basil-P
Copy link
Author

Basil-P commented May 15, 2021

Thank you Kenneth.

@jthomas
Copy link

jthomas commented Jul 29, 2021

👍 on this. I've spent a day or so debugging this confusing "feature". I couldn't find any other information as to why this was happening until I found this issue. Thanks to @Basil-P for this turning up in Google and saving me a tonne of time...

@tim-finnigan
Copy link
Contributor

P53115231

@tim-finnigan
Copy link
Contributor

The S3 team update their documentation here to add that warning. It's also here in request routing documentation. Marking this as resolved.

@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This is a problem with documentation. feature-request This issue requests a feature.
Projects
None yet
Development

No branches or pull requests

4 participants