AWS redshift: Remove RG/RA3 node requirement from federated query setup
Summary
Drops the requirement that the Redshift cluster use RG or RA3 nodes, updates the example cluster name from ra3-consumer-cluster to rg-consumer-cluster, and removes the troubleshooting bullet about RG/RA3 nodes.
Security assessment
The change only relaxes a node-type prerequisite and renames an example cluster; the VPC/security-group guidance is retained unchanged, so there is no security impact.
Evidence
-Before running the CloudFormation stack for federated queries, make sure that you have an Amazon Aurora PostgreSQL-Compatible Edition serverless database with the Data API turned on. You can turn on the Data API in the database properties. If you can't find the setting, double-check that you are running a serverless instance of Aurora PostgreSQL. Also make sure that you have a Amazon Redshift cluster that uses RG or RA3 nodes. We recommend that both the Redshift cluster and serverless Aurora PostgreSQL instance are in the same virtual private cloud (VPC) and subnet group. This way, you can add the security group for the Amazon Redshift cluster to the inbound rules of the security group for your Aurora PostgreSQL database instance.
Diff
diff --git a/redshift/latest/dg/getting-started-federated-CF.md b/redshift/latest/dg/getting-started-federated-CF.md index d8e7620..16d8ad4 100644 --- a//redshift/latest/dg/getting-started-federated-CF.md +++ b//redshift/latest/dg/getting-started-federated-CF.md @@ -19 +19 @@ If instead you want to get started with federated queries by running SQL stateme -Before running the CloudFormation stack for federated queries, make sure that you have an Amazon Aurora PostgreSQL-Compatible Edition serverless database with the Data API turned on. You can turn on the Data API in the database properties. If you can't find the setting, double-check that you are running a serverless instance of Aurora PostgreSQL. Also make sure that you have a Amazon Redshift cluster that uses RG or RA3 nodes. We recommend that both the Redshift cluster and serverless Aurora PostgreSQL instance are in the same virtual private cloud (VPC) and subnet group. This way, you can add the security group for the Amazon Redshift cluster to the inbound rules of the security group for your Aurora PostgreSQL database instance. +Before running the CloudFormation stack for federated queries, make sure that you have an Amazon Aurora PostgreSQL-Compatible Edition serverless database with the Data API turned on. You can turn on the Data API in the database properties. If you can't find the setting, double-check that you are running a serverless instance of Aurora PostgreSQL. We recommend that both the Redshift cluster and serverless Aurora PostgreSQL instance are in the same virtual private cloud (VPC) and subnet group. This way, you can add the security group for the Amazon Redshift cluster to the inbound rules of the security group for your Aurora PostgreSQL database instance. @@ -39 +39 @@ The stack creation process starts, referencing a CloudFormation template file, w - * The Amazon Redshift cluster name, for example `ra3-consumer-cluster` + * The Amazon Redshift cluster name, for example `rg-consumer-cluster` @@ -68,2 +67,0 @@ If an error occurs while the stack is created, do the following: - * Make sure that your cluster has RG or RA3 nodes. -