Bucketsquatting is (Finally) Dead
7 points by caius
7 points by caius
How are they handling the possibility of existing buckets containing the account ID of another account and the new namespace format? With the amount of buckets that exist there might be some already existing “namespace collisions”.
they could check them all
(i don't know if they did. but, they do have a list of all the buckets, so they could)
I can't imagine that there could be more than a few collisions, even with the number of existing buckets.
Im not exactly sure if/how they would convince account holders to change their bucket names however.
By saying that otherwise they will be changed for them? I would be surprised if AWS terms guaranteed "ownership" of S3 bucket names perpetually.
That's probably the best option available. I'm sure you're right that they have no legal obligation to let people keep their bucket names, but it risks pissing some people off and breaking things, even if only temporarily. With likely so few collisions, the backlash (if any) would be pretty limited I'd imagine.