Malloc for the internet: "We launched S3 in early 2006. Jeff Bezos’ original spec for S3 was very succinct – he wanted malloc (a key memory allocation function for C programs) for the Internet. From that starting point, S3 has grown to the point where it now stores many trillions of objects and processes millions of requests per second for them. Over the intervening 13 years, we have added many new storage options, features, and security controls to S3."
Amazon S3 Path Deprecation Plan – The Rest of the Story
31–40 of 146 posts
Re: Amazon S3 Path Deprecation Plan – The Rest of the Story
#32Still doesn't help with domain censorship. This was discussed in-depth in the other thread from yesterday, but TLDR, it's a lot harder to block https://s3.amazonaws.com/tiananmen-square-facts than https://tiananmen-square-facts.s3.amazonaws.com because DNS lookups are made before HTTPS kicks in.
It actually helps tremendously, since at the very least now there can be a "black market" for legacy (pre-Sept-2020) buckets, especially those on dedicated accounts that can be provided to organizations spreading facts like this.
> It actually helps tremendously, since at the very least now there can be a "black market" for legacy (pre-Sept-2020) buckets
Err, no, countries will just block the legacy bucket URL style and say that only the bad guys would still be using it.
Re: Amazon S3 Path Deprecation Plan – The Rest of the Story
#33Earlier quoted context omitted.
What could Amazon do that would "help"?
Still let people use the old path system, even on new servers. This is an often-used trick to get around government censorship that will be destroyed with this change.
Why S3 must carry the burden of getting around censorship?
If you are talking about China, yeah, Google used to carry that burden. Now GAE, GCloud, Youtube, Gmail are all gone. The whole IP range was blacklisted.
Now what?
Just because something accidentally works does not mean it will last forever.
Re: Amazon S3 Path Deprecation Plan – The Rest of the Story
#34Earlier quoted context omitted.
It actually helps tremendously, since at the very least now there can be a "black market" for legacy (pre-Sept-2020) buckets, especially those on dedicated accounts that can be provided to organizations spreading facts like this.
> It actually helps tremendously, since at the very least now there can be a "black market" for legacy (pre-Sept-2020) buckets Err, no, countries will just block the legacy bucket URL style and say that only the bad guys would still be using it.
That would mean they are blocking all S3 buckets indiscriminately.
Re: Amazon S3 Path Deprecation Plan – The Rest of the Story
#35Earlier quoted context omitted.
It actually helps tremendously, since at the very least now there can be a "black market" for legacy (pre-Sept-2020) buckets, especially those on dedicated accounts that can be provided to organizations spreading facts like this.
> It actually helps tremendously, since at the very least now there can be a "black market" for legacy (pre-Sept-2020) buckets Err, no, countries will just block the legacy bucket URL style and say that only the bad guys would still be using it.
If they went to that extreme maybe they’d block AWS altogether. Or all SSL traffic!
Re: Amazon S3 Path Deprecation Plan – The Rest of the Story
#36> Bucket Names with Dots – It is important to note that bucket names with “.” characters are perfectly valid for website hosting and other use cases. However, there are some known issues with TLS and with SSL certificates. We are hard at work on a plan to support virtual-host requests to these buckets, and will share the details well ahead of September 30, 2020. I’m mystified how they’re planning on doing this. Anybo…
Use some kind of encoding? Maybe a type of Punycode?
Re: Amazon S3 Path Deprecation Plan – The Rest of the Story
#37Earlier quoted context omitted.
What could Amazon do that would "help"?
Still let people use the old path system, even on new servers. This is an often-used trick to get around government censorship that will be destroyed with this change.
TBH, though, I'm not sure that would really help that much over time. It's clear there are real benefits for having bucket names in subdomains, such that the majority of new users would pick that format in any case. In that situation, governments may end up just blocking s3.amazon.com in any case because "only old bad guys" continue to use it.
Re: Amazon S3 Path Deprecation Plan – The Rest of the Story
#38Earlier quoted context omitted.
> It actually helps tremendously, since at the very least now there can be a "black market" for legacy (pre-Sept-2020) buckets Err, no, countries will just block the legacy bucket URL style and say that only the bad guys would still be using it.
If they went to that extreme maybe they’d block AWS altogether. Or all SSL traffic!
People didn't seem to remember that the exact thing happened to Google. Picasa, youtube, GCloud, GSuite, and finally Gmail.
Who's next, domain fronting on Microsoft Azure?
Re: Amazon S3 Path Deprecation Plan – The Rest of the Story
#39Still doesn't help with domain censorship. This was discussed in-depth in the other thread from yesterday, but TLDR, it's a lot harder to block https://s3.amazonaws.com/tiananmen-square-facts than https://tiananmen-square-facts.s3.amazonaws.com because DNS lookups are made before HTTPS kicks in.
However, encrypted SNI and DNS-over-HTTPS should provide a better solution to that problem once they're ready, and there's no reason to think Amazon won't adopt encrypted SNI.
Re: Amazon S3 Path Deprecation Plan – The Rest of the Story
#40For anyone still confused to why AWS dominates the cloud market, it's because they're willing to grandfather features with a reasonable sunset horizon.