I wonder how they’ll handle capitalized bucket names. This seems like it will break that. S3 has been around a long time, and they made some decisions early on

I wonder how they’ll handle capitalized bucket names. This seems like it will break that. S3 has been around a long time, and they made some decisions early on that they realised wouldn’t scale, so they reversed them. This v1 vs v2 url thing is one of them. But another was letting you have “BucketName” and “bucketname” as two distinct buckets. You can’t name them like that today, but you could at first, and they still work (and are in conflict under v2 naming). Amazons own docs explain that you still need to use the old v1 scheme for capitalized names, as well as names containing certain special characters. It’d be a shame if they just tossed all those old buckets in the trash by leaving them inaccessible. All in, this seems like another silly, unnecessary, depreciation of an API that was working perfectly well. A trend I’m noticing more often these days. Shame.