AWS redshift documentation change
Summary
Updated cluster relocation default behavior to be enabled for new/restored RA3 clusters in multi-AZ subnet groups. Added mention of Enhanced VPC Routing in access instructions.
Security assessment
The change modifies default configuration behavior but does not address a specific security vulnerability. The Enhanced VPC Routing mention clarifies existing network security best practices rather than introducing new security controls.
Diff
diff --git a/redshift/latest/mgmt/managing-cluster-recovery.md b/redshift/latest/mgmt/managing-cluster-recovery.md index 95b8a0601..ba6dce09d 100644 --- a//redshift/latest/mgmt/managing-cluster-recovery.md +++ b//redshift/latest/mgmt/managing-cluster-recovery.md @@ -19 +19 @@ When you turn on relocation for your cluster, Amazon Redshift migrates your clus -Cluster relocation is disabled by default on all RA3 clusters. Amazon Redshift assigns 5439 as the default port while creating a provisioned cluster. You can change to another port from the port range of 5431-5455 or 8191-8215. (Don't change to a port outside the ranges. It results in an error.) To change the default port for a provisioned cluster, use the Amazon Redshift console, AWS CLI, or Amazon Redshift API. To change the default port for a serverless workgroup, use the AWS CLI or the Amazon Redshift Serverless API. +Cluster relocation is enabled by default on newly created or restored RA3 clusters whose subnet group includes multiple Availability Zones. Amazon Redshift assigns 5439 as the default port while creating a provisioned cluster. You can change to another port from the port range of 5431-5455 or 8191-8215. (Don't change to a port outside the ranges. It results in an error.) To change the default port for a provisioned cluster, use the Amazon Redshift console, AWS CLI, or Amazon Redshift API. To change the default port for a serverless workgroup, use the AWS CLI or the Amazon Redshift Serverless API. @@ -21 +21 @@ Cluster relocation is disabled by default on all RA3 clusters. Amazon Redshift a -If you turn on relocation and you currently use the leader node IP address to access your cluster, make sure to change that access. Instead, use the IP address associated with the cluster's virtual private cloud (VPC) endpoint. To find this cluster IP address, find and use the VPC endpoint in the **Network and security** section of the cluster details page. To get more details on the VPC endpoint, sign in to the Amazon VPC console. +If you turn on relocation and you currently use the leader node IP address to access your your cluster or Enhanced VPC Routing, make sure to change that access. Instead, use the IP address associated with the cluster's virtual private cloud (VPC) endpoint. To find this cluster IP address, find and use the VPC endpoint in the **Network and security** section of the cluster details page. To get more details on the VPC endpoint, sign in to the Amazon VPC console.