Hacker News Reader

I'm so impressed at how S3 can roll out changes like this on a regularly frequent basis that impact an unimaginably large number of servers and stored data.

This is an incredible piece of engineering. Almost as impressive as when they made S3 read-after-write consistent a couple of years ago: https://aws.amazon.com/blogs/aws/amazon-s3-update-strong-rea...

View on HN

The only thing impressive about this is how long it’s taken them to make this the default. This has been available since 2011 and other cloud providers have had encryption at rest by default for years.

The read-after-write consistency was definitely an impressive change. This however, not so much.

Encryption enabled by default at different S3 compatible providers:

- [x] Microsoft Azure (https://learn.microsoft.com/en-us/azure/storage/common/stora...)

- [x] Google Cloud Storage (https://cloud.google.com/storage/docs/encryption)

- [x] Backblaze B2 (https://help.backblaze.com/hc/en-us/articles/217973398-Encry...)

- [x] Wasabi (https://wasabi-support.zendesk.com/hc/en-us/articles/1150016...)

- [ ] DigitalOcean (https://www.digitalocean.com/community/tutorials/how-to-crea...)

- [ ] DreamHost (https://help.dreamhost.com/hc/en-us/articles/360001089163-En...)

- [ ] Linode (https://www.linode.com/docs/guides/server-side-encryption/)

Reply on news.ycombinator.com