-
Notifications
You must be signed in to change notification settings - Fork 17
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
Switch to using virtual-host style URLs when possible #49
Comments
danielcompton
changed the title
Allow using the hostname based bucket URL
Switch to using virtual-host style URLs when possible
Sep 24, 2019
Also, from Working with Amazon S3 Buckets:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, s3-beam uses
https://s3-<region>.amazonaws.com/<bucket>
as the upload URL path (path-style). It is also possible to upload tohttps://<bucket>.s3-<region>.amazonaws.com
(virtual-host style).AWS is planning to deprecate path-style addressing for buckets created after September 30, 2020. There are also performance and resilience benefits for switching to virtual-host style addressing for existing buckets.
The switch is transparent for many buckets, but is not for buckets with a
.
in the bucket name (among others). AWS doesn't currently create a valid certificate for these buckets, so you will get TLS errors when you try to upload/download from them.Using #38 would fix this for us, as it defaults to using virtual-host style addressing, unless the bucket has a
.
in it.In the meantime, you can use the
upload-url
parameter tos3-sign
to override the upload URL.The text was updated successfully, but these errors were encountered: