Hacker News new | ask | show | jobs
by Liquid_Fire 3180 days ago
They could make it configurable on a per bucket basis (perhaps defaulting to the old behaviour if necessary; ideally you would make the conformant behaviour the default, of course).

That way you could opt in to the standard conformant behaviour if you require it, but they can still keep backward compatibility.

2 comments

I'm not familiar with how S3 works in detail, but I imagine this could require additional API calls in the backend which increases the latency and resource usage of API requests. In the worst case, such a change could easily require Amazon to purchase dozens, if not hundreds of additional servers.
With the rate of AWS growth, they probably bought dozens more servers in the time it took you to write out your response. :)
Likely, but Amazon didn't get where they are by ignoring small costs.
Or use a different domain for the same buckets, and resolve the name correctly on this new domain.