-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Comments
Hi @Basil-P, thanks for bringing this up. I'll review this with the docs writers. |
Thank you Kenneth. |
👍 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... |
P53115231 |
|
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 :-)
The text was updated successfully, but these errors were encountered: