- Newest
- Most votes
- Most comments
You can't use built-on KMS key for Redshift on another account.
Thank you Anusha. Since the source key is an AWS managed key, is it still possible to do what you described? I can edit the key policy for customer managed keys but don't appear to have the same option to edit key policy for AWS managed keys. It could be my access level but maybe the key policy can't be edited for AWS managed keys?
In the source account, provide access on the KMS Key used for encryption to the target account. In order to do it, you can follow the steps below:
- In AWS Management console of the source account, navigate to KMS
- Click on the KMS key that was used to encrypt the cluster
- Click on the Edit button in the Key Policy tab
- Update the Key policy to add the principal for destination account as shown in the sample policy below
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": [
"arn:aws:iam::{SourceAccountID}:root",
"arn:aws:iam::{DestinationAccountID}:root"
]
},
"Action": "kms:*",
"Resource": "*"
}
]
}
Once you provide access on KMS key to destination account's principal, re-try snapshot restore.
If you are using an AWS managed, Key policy cannot be updated. In such case, you can change they KMS key during restore process. In the restore screen, under Additional configurations, provide the key you want to use for Choose an AWS KMS key. This can be the AWS managed redshift key from the target account.
Please note that restore process takes longer when the key is changed during restore process.
The restore process moves users, groups along with data.
On more research we found that we can't share or edit the policy of an AWS managed key. We were able to unecrypt and re-encrypt a test cluster to a customer managed key but we do not want the state of the production cluster to ever be unencrypted - even during this process. We tried changing they aws key to our key directly in the console but got the error below. InvalidParameterValue You can't transform a cluster with KMS encryption type to KMS encryption type.
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Key policy on AWS managed keys cannot be updated. However, you can change they KMS key during restore process. Under Additional configurations, provide the key you want to use for Choose an AWS KMS key. This can be the AWS managed redshift key from the account.
Please note that restore process takes longer when the key is changed during restore process.