Amazon Explains, Changes its S3 Path Deprecation Plan

Last week, Amazon announced a plan to end path-style API requests for its AWS S3 object storage solution starting on September 30, 2020. Currently, Amazon offers S3 users the ability to choose between two URI styles -- path-style and virtual-hosted style -- but explained that as part of its "continuously improve customer experience", had decided to retire path-style requests in favor of virtual-hosted style requests.

While observers noted a number of technical reasons why such a move made sense for Amazon, the announcement sparked push-back, especially from developers who make extensive use of path-style requests.

In response, Jeff Barr, Amazon's chief evangelist for AWS, explained Amazon's decision in more detail. "First, anticipating a world with billions of buckets homed in many dozens of regions, routing all incoming requests directly to a small set of endpoints makes less and less sense over time," he wrote in a blog post, adding that Amazon also has new features under development that will require virtual-hosted style requests.

To mitigate the effects of its plan, however, Barr announced that instead of forcing developers to change by September 30, 2020, Amazon will maintain support for path-style requests for S3 buckets that are created on or before this date. All buckets created after September 30, 2020 will need to use virtual-hosted style requests, but the altered plans offers relief to developers who already have large numbers of S3 objects making use of path-style requests.

Be sure to read the next Storage article: How APIs Can Standardize Information Storage in the Cloud