Changing the Amazon KMS key for a namespace
In Amazon Redshift, encryption protects data at rest. Amazon Redshift Serverless uses Amazon KMS key encryption automatically to encrypt both your Amazon Redshift Serverless resources and snapshots. As a best practice, most organizations review the type of data they store and have a plan to rotate encryption keys on a schedule. The frequency for rotating keys can vary, depending on your policies for data security. Amazon Redshift Serverless supports changing the Amazon KMS key for the namespace so you can adhere to your organization's security policies.
When you change the Amazon KMS key, the data remains unchanged.
Changing an Amazon KMS key using the console
In Amazon Redshift, encryption protects data at rest. Amazon Redshift Serverless uses Amazon KMS key encryption automatically to encrypt both Amazon Redshift Serverless and snapshots. As a best practice, most organizations review the type of data they store and have a plan to rotate encryption keys on a schedule. The frequency for rotating keys can vary, depending on your policies for data security. Amazon Redshift Serverless supports changing the Amazon KMS key for the namespace so you can adhere to your organization's security policies.
When you change the Amazon KMS key, the data remains unchanged.
Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshiftv2/
. -
On the navigation menu, choose Namespace configuration. Choose your namespace from the list.
-
From the Security and encryption tab, choose Edit.
-
Choose Customize encryption settings and then choose a key for the namespace. You can optionally create a new key.
Changing Amazon KMS encryption keys using the Amazon CLI
Use update-namespace to change the Amazon KMS key for the
namespace. The following shows the syntax for the command:
aws redshift-serverless update-namespace --namespace-name [--kms-key-id <id-of-kms-key>] // other parameters omitted here
You must have a namespace created or the CLI command results in an error.
The time it takes to change the key depends on the amount of data in Amazon Redshift Serverless. This typically takes fifteen minutes per 8TB of stored data.
Limitations
You can’t change from a customer managed KMS Key to an Amazon KMS key. In this case, you have to create a new namespace.
You can’t perform other actions while the key is being changed.