You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An unfortunate announcement on the AWS Developer Forums started doing the rounds today:
Amazon S3 currently supports two request URI styles in all regions: path-style (also known as V1) that includes bucket name in the path of the URI (example: //s3.amazonaws.com//key), and virtual-hosted style (also known as V2) which uses the bucket name as part of the domain name (example: //.s3.amazonaws.com/key). In our effort to continuously improve customer experience, the path-style naming convention is being retired in favor of virtual-hosted style request format. Customers should update their applications to use the virtual-hosted style request format when making S3 API requests before September 30th, 2020 to avoid any service disruptions. Customers using the AWS SDK can upgrade to the most recent version of the SDK to ensure their applications are using the virtual-hosted style request format.
Virtual-hosted style requests are supported for all S3 endpoints in all AWS regions. S3 will stop accepting requests made using the path-style request format in all regions starting September 30th, 2020. Any requests using the path-style request format made after this time will fail.
I guess that means that the "easy mode" path-based workflow I've been incrementally adding support for is on the way out the door, so we should probably shift back to improving the experience for DNS-based workflows.
Is there any way we can emulate the virtual-host style thing in a way that is turn-key for devs (i.e. not requiring them to futz around with their DNS setup manually)?
The text was updated successfully, but these errors were encountered:
Just seen it as well. Good question in regards to the DNS setup. I'm only aware about mDNS and/or /etc/hosts changes. I'll take a further look as well.
Original Plan – Support for the path-style model ends on September 30, 2020.
Revised Plan – Support for the path-style model continues for buckets created on or before September 30, 2020. Buckets created after that date must be referenced using the virtual-hosted model.
An unfortunate announcement on the AWS Developer Forums started doing the rounds today:
I guess that means that the "easy mode" path-based workflow I've been incrementally adding support for is on the way out the door, so we should probably shift back to improving the experience for DNS-based workflows.
Is there any way we can emulate the virtual-host style thing in a way that is turn-key for devs (i.e. not requiring them to futz around with their DNS setup manually)?
The text was updated successfully, but these errors were encountered: