AWS redshift documentation change
Summary
Updated subnet and Availability Zone requirements for Redshift Serverless workgroups (EVR vs. non-EVR)
Security assessment
Clarifies infrastructure requirements but does not address security vulnerabilities or document security features.
Diff
diff --git a/redshift/latest/mgmt/serverless-usage-considerations.md b/redshift/latest/mgmt/serverless-usage-considerations.md index 6e7ba3627..0bd6f9301 100644 --- a//redshift/latest/mgmt/serverless-usage-considerations.md +++ b//redshift/latest/mgmt/serverless-usage-considerations.md @@ -19 +19 @@ _Track_ – When Amazon Redshift releases a new workgroup version, your workgrou -_Availability Zone IDs_ – When you configure your Amazon Redshift Serverless instance, open **Additional considerations** , and make sure that the subnet IDs provided in **Subnet** contain at least three of the supported Availability Zone IDs. To see the subnet to Availability Zone ID mapping, go to the VPC console and choose **Subnets** to see the list of subnet IDs with their Availability Zone IDs. Verify that your subnet is mapped to a supported Availability Zone ID. To create a subnet, see [Create a subnet in your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html#AddaSubnet) in the _Amazon VPC User Guide_. +_Availability Zone IDs_ – When you configure your Amazon Redshift Serverless instance, open **Additional considerations** , and make sure that the subnet IDs provided in **Subnet** contain at least two of the supported Availability Zone IDs. @@ -21 +21,12 @@ _Availability Zone IDs_ – When you configure your Amazon Redshift Serverless i -_Three subnets_ – You must have at least three subnets, and they must span across three Availability Zones. For example, you might use three subnets that map to the Availability Zones us-east-1a, us-east-1b, and us-east-1c. An exception to this is the US West (N. California) Region. It requires three subnets, in the same manner as the other regions, but these must span across only two Availability Zones. A condition is that one of the Availability Zones spanned must contain two of the subnets. + * For workgroups without Enhanced VPC Routing (EVR), you need two Availability Zones (AZs). + + * For workgroups with EVR, you need three AZs. + + + + +To see the subnet to Availability Zone ID mapping, go to the VPC console and choose **Subnets** to see the list of subnet IDs with their Availability Zone IDs. Verify that your subnet is mapped to a supported Availability Zone ID. To create a subnet, see [Create a subnet in your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html#AddaSubnet) in the _Amazon VPC User Guide_. + +_Two subnets (without EVR)_ – You must have at least two subnets, and they must span across two Availability Zones. + +_Three subnets (with EVR ONLY)_ – You must have at least three subnets when you use EVR, and they must span across three or more Availability Zones.