Amazon Aurora now supports Server-Side Encryption by default

Amazon Aurora further strengthens your security posture by automatically applying server-side encryption by default to all new databases clusters, created starting today, using [AWS-owned keys](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-owned-key). This encryption is fully managed, transparent to users, with no cost or performance impact. Aurora now automatically encrypts all new database clusters created without custom encryption settings using server-side encryption by default. Existing clusters remain unaffected and you can continue using the current encryption configuration with customer-managed or AWS-managed KMS keys.This automatic encryption only applies to new clusters where no encryption configuration is provided. You cannot disable encryption on new clusters, but can choose customer-managed or AWS-managed KMS keys instead of server side encryption during cluster creation. Server side encryption provides encryption protection without requiring you to provision, rotate, or manage keys. This update is available in all [AWS Regions](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/), including the [AWS GovCloud (US) Regions](https://aws.amazon.com/govcloud-us/). To learn more about encryption at rest, refer to our [blog](https://aws.amazon.com/blogs/database/use-default-encryption-at-rest-for-new-amazon-aurora-clusters/) or see [Aurora encryption documentation](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Overview.Encryption.html).