Amazon Redshift Update: This release adds a new [--encrypted | --no-encrypted] field in restore-from-cluster-snapshot API. Customers can now restore an unencrypted snapshot to a cluster encrypted with AWS Managed Key or their own KMS key.

Author: AWS

.changes/next-release/feature-AmazonRedshift-af24895.json

@@ -0,0 +1,6 @@
+{
+    "type": "feature",
+    "category": "Amazon Redshift",
+    "contributor": "",
+    "description": "This release adds a new [--encrypted | --no-encrypted] field in restore-from-cluster-snapshot API. Customers can now restore an unencrypted snapshot to a cluster encrypted with AWS Managed Key or their own KMS key."
+}

services/redshift/src/main/resources/codegen-resources/service-2.json

@@ -8541,7 +8541,7 @@
         },
         "KmsKeyId":{
           "shape":"String",
-          "documentation":"<p>The Key Management Service (KMS) key ID of the encryption key that you want to use to encrypt data in the cluster that you restore from a shared snapshot.</p>"
+          "documentation":"<p>The Key Management Service (KMS) key ID of the encryption key to encrypt data in the cluster restored from a shared snapshot. You can also provide the key ID when you restore from an unencrypted snapshot to an encrypted cluster in the same account. Additionally, you can specify a new KMS key ID when you restore from an encrypted snapshot in the same account in order to change it. In that case, the restored cluster is encrypted with the new KMS key ID.</p>"
         },
         "NodeType":{
           "shape":"String",
@@ -8590,6 +8590,10 @@
         "TargetReservedNodeOfferingId":{
           "shape":"String",
           "documentation":"<p>The identifier of the target reserved node offering.</p>"
+        },
+        "Encrypted":{
+          "shape":"BooleanOptional",
+          "documentation":"<p>Enables support for restoring an unencrypted snapshot to a cluster encrypted with Key Management Service (KMS) and a CMK.</p>"
         }
       },
       "documentation":"<p/>"