-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Passing endpoint_url to s3 client will alter s3 key #4307
Comments
Hi @runawaycoast, thanks for reaching out. Can you go into more detail about why you are specifying an endpoint_url? An S3 client without specifying an endpoint_url would automatically connect to the S3 endpoint. Specifying an endpoint_url is only necessary if you're using non-AWS S3 storage. Thanks! |
Hi, @adev-code Thanks for taking a look at this issue. I was using endpoint_url to point to localstack for my local development, but instead of setting it to None for higher environment, I set it to the bucket url. I am just to point out the issue and see if we can solve the inconsistent behavior. |
Hi @runawaycoast, thanks for the update. When endpoint_url is used, it only has to be
Please let me know if you have any follow up questions. Thanks. |
Thank you so much for providing the solution in detail, no further questions from my side. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the bug
When pass the endpoint_url to constructor of boto3 s3 client, it will alter the key on uploading by adding the bucket name as prefix
tmp/test.txt becomes bucket_name/tmp/text.txt
Regression Issue
Expected Behavior
passing endpoint_url should not create a new folder and alter the s3 object key
Current Behavior
it alters the intended s3 key
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
SDK version used
1.35.41
Environment details (OS name and version, etc.)
Debian GNU/Linux 12 (bookworm)
The text was updated successfully, but these errors were encountered: