AWS redshift: Add Zurich region and RG node sizing guidance
Summary
Documents availability of RG node types in Europe (Zurich) and rewrites upgrade guidance to recommend benchmarking RG workloads and adjusting node counts, noting RG is lower cost per vCPU than RA3.
Security assessment
The changes add a supported AWS Region and expand performance/cost guidance for RG node upgrades; no authentication, encryption, permissions, or vulnerability content is involved.
Evidence
+ * Europe (Zurich) Region (eu-central-2)
Diff
diff --git a/redshift/latest/mgmt/managing-cluster-considerations.md b/redshift/latest/mgmt/managing-cluster-considerations.md index 609241b1e..22bf82495 100644 --- a//redshift/latest/mgmt/managing-cluster-considerations.md +++ b//redshift/latest/mgmt/managing-cluster-considerations.md @@ -272,0 +273,2 @@ The RG node types are available only in the following AWS Regions: + * Europe (Zurich) Region (eu-central-2) + @@ -398 +400,3 @@ The following table shows recommendations when upgrading to RG node types. (Thes -The recommendations in this table are starting cluster node types and sizes but depend on the computing requirements of your workload. To better estimate your requirements, consider conducting a proof of concept (POC) that uses [Test Drive](https://github.com/aws/redshift-test-drive/tree/main) to run potential configurations. Provision a cluster for your POC data warehouse instead of Redshift Serverless. For more information about conducting a proof of concept, see [Conduct a proof of concept (POC) for Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/dg/proof-of-concept-playbook.html) in the _Amazon Redshift Database Developer Guide_. +The recommendations in this table are starting cluster node types and sizes but depend on the computing requirements of your workload. RG has different performance characteristics, so the recommended mapping is a starting point. Benchmark your critical workloads and adjust the number of nodes up or down based on observed performance. RG instances are lower in price per vCPU compared to RA3, so adding nodes to optimize performance can still result in lower overall cost. For more information about node type pricing, see [Amazon Redshift pricing](https://aws.amazon.com/redshift/pricing/). + +To better estimate your requirements, consider conducting a proof of concept (POC) that uses [Test Drive](https://github.com/aws/redshift-test-drive/tree/main) to run potential configurations. Provision a cluster for your POC data warehouse instead of Redshift Serverless. For more information about conducting a proof of concept, see [Conduct a proof of concept (POC) for Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/dg/proof-of-concept-playbook.html) in the _Amazon Redshift Database Developer Guide_. @@ -413 +417 @@ dc2.large | 16–32 | rg.4xlarge | Start with 1 node of rg.4xlarge for every 10 -1Extra nodes might be needed depending on workload requirements. Add or remove nodes based on the compute requirements of your required query performance. +1Extra nodes might be needed depending on workload requirements. Add or remove nodes based on the compute requirements of your required query performance. RG instances are lower in price per vCPU compared to RA3, so adding nodes can still result in lower overall cost compared to your previous configuration. For more information, see [Amazon Redshift pricing](https://aws.amazon.com/redshift/pricing/).