AWS redshift documentation change
Summary
Updated documentation to include RG clusters alongside RA3 clusters in no-backup table behavior descriptions, event emission details, and node type examples. Modified restore cluster example to use RA3 node types instead of DC2, updated recommended configurations, and changed reserved node upgrade references from RA3 to RG.
Security assessment
Changes involve feature documentation updates (adding RG cluster support and updating node type examples). No security vulnerabilities, patches, or weaknesses are mentioned. Modifications focus on functionality and example configurations without introducing security controls or addressing security incidents.
Diff
diff --git a/redshift/latest/mgmt/working-with-snapshot-restore-cluster-from-snapshot.md b/redshift/latest/mgmt/working-with-snapshot-restore-cluster-from-snapshot.md index cc724b8d0..4a7916e13 100644 --- a//redshift/latest/mgmt/working-with-snapshot-restore-cluster-from-snapshot.md +++ b//redshift/latest/mgmt/working-with-snapshot-restore-cluster-from-snapshot.md @@ -15 +15 @@ A snapshot contains data from any databases that are running on your cluster. It -No-backup tables aren't supported for RA3 provisioned clusters and Amazon Redshift Serverless workgroups. A table marked as no-backup in an RA3 cluster or serverless workgroup is treated as a permanent table that will always be backed up while taking a snapshot, and always restored when restoring from a snapshot. +No-backup tables aren't supported for RG or RA3 provisioned clusters and Amazon Redshift Serverless workgroups. A table marked as no-backup in an RG or RA3 cluster or serverless workgroup is treated as a permanent table that will always be backed up while taking a snapshot, and always restored when restoring from a snapshot. @@ -38 +38 @@ The cluster is available for queries. -RA3 clusters only emit RESTORE_STARTED and RESTORE_SUCCEEDED events. There is no explicit data transfer to be done after a RESTORE succeeds because RA3 node types store data in Amazon Redshift managed storage. With RA3 nodes, data is continuously transferred between RA3 nodes and Amazon Redshift managed storage as part of normal query processing. RA3 nodes cache hot data locally and keep less frequently queried blocks in Amazon Redshift managed storage automatically. +RG and RA3 clusters only emit RESTORE_STARTED and RESTORE_SUCCEEDED events. There is no explicit data transfer to be done after a RESTORE succeeds because RG and RA3 node types store data in Amazon Redshift managed storage. With RG and RA3 nodes, data is continuously transferred between RG and RA3 nodes and Amazon Redshift managed storage as part of normal query processing. RG and RA3 nodes cache hot data locally and keep less frequently queried blocks in Amazon Redshift managed storage automatically. @@ -84 +84 @@ The following steps take a cluster with many nodes and consolidate it into a big -This command returns an option list with recommended node types, number of nodes, and disk utilization for each option. For this example, the preceding command lists the following possible node configurations. We choose to restore into a three-node cluster. +This command returns an option list with recommended node types, number of nodes, and disk utilization for each option. For this example, the preceding command lists the following possible node configurations. We choose to restore into a four-node cluster. @@ -89,8 +89,3 @@ This command returns an option list with recommended node types, number of nodes - "EstimatedDiskUtilizationPercent": 65.26134808858235, - "NodeType": "dc2.large", - "NumberOfNodes": 24 - }, - { - "EstimatedDiskUtilizationPercent": 32.630674044291176, - "NodeType": "dc2.large", - "NumberOfNodes": 48 + "NodeType": "ra3.16xlarge", + "NumberOfNodes": 2, + "EstimatedDiskUtilizationPercent": 0.1 @@ -99,3 +94,3 @@ This command returns an option list with recommended node types, number of nodes - "EstimatedDiskUtilizationPercent": 65.26134808858235, - "NodeType": "dc2.8xlarge", - "NumberOfNodes": 3 + "NodeType": "ra3.16xlarge", + "NumberOfNodes": 4, + "EstimatedDiskUtilizationPercent": 0.05 @@ -104,3 +99,13 @@ This command returns an option list with recommended node types, number of nodes - "EstimatedDiskUtilizationPercent": 48.94601106643677, - "NodeType": "dc2.8xlarge", - "NumberOfNodes": 4 + "NodeType": "ra3.4xlarge", + "NumberOfNodes": 8, + "EstimatedDiskUtilizationPercent": 0.03 + }, + { + "NodeType": "ra3.4xlarge", + "NumberOfNodes": 10, + "EstimatedDiskUtilizationPercent": 0.02 + }, + { + "NodeType": "ra3.4xlarge", + "NumberOfNodes": 12, + "EstimatedDiskUtilizationPercent": 0.02 @@ -109,3 +114,3 @@ This command returns an option list with recommended node types, number of nodes - "EstimatedDiskUtilizationPercent": 39.156808853149414, - "NodeType": "dc2.8xlarge", - "NumberOfNodes": 5 + "NodeType": "ra3.xlplus", + "NumberOfNodes": 8, + "EstimatedDiskUtilizationPercent": 0.11 @@ -114,3 +119,3 @@ This command returns an option list with recommended node types, number of nodes - "EstimatedDiskUtilizationPercent": 32.630674044291176, - "NodeType": "dc2.8xlarge", - "NumberOfNodes": 6 + "NodeType": "ra3.xlplus", + "NumberOfNodes": 16, + "EstimatedDiskUtilizationPercent": 0.06 @@ -121 +126 @@ This command returns an option list with recommended node types, number of nodes - 4. Run the following command to restore the snapshot into the cluster configuration that we chose. After this cluster is restored, we have the same content as the source cluster, but the data has been consolidated into three `dc2.8xlarge` nodes. + 4. Run the following command to restore the snapshot into the cluster configuration that we chose. After this cluster is restored, we have the same content as the source cluster, but the data has been consolidated into four `ra3.16xlarge` nodes. @@ -123 +128 @@ This command returns an option list with recommended node types, number of nodes - aws redshift restore-from-cluster-snapshot --region eu-west-1 --snapshot-identifier mycluster-snapshot --cluster-identifier mycluster-123456789012-x --node-type dc2.8xlarge --number-of-nodes 3 + aws redshift restore-from-cluster-snapshot --region eu-west-1 --snapshot-identifier mycluster-snapshot --cluster-identifier mycluster-123456789012-x --node-type ra3.16xlarge --number-of-nodes 4 @@ -128 +133 @@ This command returns an option list with recommended node types, number of nodes -If you have reserved nodes, for example DC2 reserved nodes, you can upgrade to RA3 reserved nodes. You can do this when you restore from a snapshot or perform an elastic resize. You can use the console to guide you through this process. For more information about upgrading to RA3 nodes, see [Upgrading to RA3 node types](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-upgrading-to-ra3). +If you have reserved nodes, for example RA3 reserved nodes, you can upgrade to RG reserved nodes. You can do this when you restore from a snapshot or perform an elastic resize. You can use the console to guide you through this process. For more information about upgrading to RG nodes, see [Upgrading to RG node types](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-upgrading-to-rg). @@ -163 +168 @@ If AWS Secrets Manager managed your cluster's admin password at the time the sna -If you have reserved nodes, you can upgrade to RA3 reserved nodes. You can do this when you restore from a snapshot or perform an elastic resize. You can use the console to guide you through this process. For more information about upgrading to RA3 nodes, see [Upgrading to RA3 node types](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-upgrading-to-ra3). +If you have reserved nodes, you can upgrade to RG reserved nodes. You can do this when you restore from a snapshot or perform an elastic resize. You can use the console to guide you through this process. For more information about upgrading to RG nodes, see [Upgrading to RG node types](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-upgrading-to-rg).