New Buckets Are Encrypted by Default Again
Server-side encryption at rest is back on by default for every new bucket, now that server-side copies of encrypted objects work.
What's changed
- Buckets created in the dashboard and through the API both default to encryption at rest; previously only the API did
- You can still opt out per bucket when you create it
- CopyObject now works on encrypted objects, so client-side move and rename operations succeed; multipart copies (UploadPartCopy) of encrypted objects remain partially supported