AWS redshift documentation change
Summary
Added note about default KMS keys and JSON formatting markers
Security assessment
Clarifies security implications of using default KMS keys for snapshot sharing
Diff
diff --git a/redshift/latest/mgmt/working-with-snapshot-share-snapshot.md b/redshift/latest/mgmt/working-with-snapshot-share-snapshot.md index 306eab4dc..1ccc221df 100644 --- a//redshift/latest/mgmt/working-with-snapshot-share-snapshot.md +++ b//redshift/latest/mgmt/working-with-snapshot-share-snapshot.md @@ -20,0 +21,6 @@ After you have authorized access to an AWS customer account, no users in that ac +JSON + + +**** + + @@ -40,0 +48,6 @@ After you have authorized access to an AWS customer account, no users in that ac +JSON + + +**** + + @@ -57,0 +72,6 @@ After you have authorized access to an AWS customer account, no users in that ac +JSON + + +**** + + @@ -101,0 +123,4 @@ The customer managed key policy can be updated programmatically or in the AWS Ke +###### Note + +If you're using a default KMS key, you don't need to take action or change anything in AWS KMS in order to share a snapshot. + @@ -114,0 +140,6 @@ In the following key-policy example, user `111122223333` is the owner of the KMS +JSON + + +**** + +