AWS redshift documentation change
Summary
Enhanced maintenance window details and updated multiple documentation links
Security assessment
Added operational details about maintenance windows and URL formatting. While maintenance updates could indirectly affect availability, there's no evidence of addressing security vulnerabilities or adding security features.
Diff
diff --git a/redshift/latest/mgmt/serverless-usage-considerations.md b/redshift/latest/mgmt/serverless-usage-considerations.md index 05bf169a7..4a2c4a8dc 100644 --- a//redshift/latest/mgmt/serverless-usage-considerations.md +++ b//redshift/latest/mgmt/serverless-usage-considerations.md @@ -15 +15 @@ When you DECLARE a cursor, the result-set size specifications for Amazon Redshif -_Maintenance window_ – There is no maintenance window with Amazon Redshift Serverless. Software version updates are automatically applied. There's no interruption for existing connection or query execution when Amazon Redshift switches versions. New connections will always connect and work with Amazon Redshift Serverless instantly. +_Maintenance Window_ – Amazon Redshift Serverless offers automatic software updates without requiring traditional maintenance windows. When a new update is available, the system applies it within 14 days of release during idle periods. The update process typically takes up to 15 minutes. If no 15-minute idle period occurs within 14 days, your Serverless endpoint may experience brief unavailability. During this time, application connections to endpoints may fail. You can monitor Redshift patch releases in the "Cluster versions for Amazon Redshift" documentation. For information about Amazon Redshift Serverless SLAs, see [Amazon Redshift Service Level Agreement](https://aws.amazon.com/redshift/sla/). @@ -28 +28 @@ _Availability Zone IDs_ – When you configure your Amazon Redshift Serverless i -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_. +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_. @@ -92 +92 @@ The maximum base RPU capacity of 1024 is only available in the following AWS Reg -For more information on allocating IP addresses, see [IP addressing](https://docs.aws.amazon.com/vpc/latest/userguide/how-it-works.html#vpc-ip-addressing) in the _Amazon VPC User Guide_. +For more information on allocating IP addresses, see [IP addressing](https://docs.aws.amazon.com//vpc/latest/userguide/how-it-works.html#vpc-ip-addressing) in the _Amazon VPC User Guide_. @@ -100 +100 @@ _Max query execution time_ – Elapsed execution time for a query, in seconds. E -_Migrating for tables with interleaved sort keys_ – When migrating Amazon Redshift provisioned clusters to Amazon Redshift Serverless, Redshift converts tables with interleaved sort keys and DISTSTYLE KEY to compound sort keys. The DISTSTYLE doesn't change. For more information on distribution styles, see [Working with data distribution styles](https://docs.aws.amazon.com/redshift/latest/dg/t_Distributing_data.html) in the Amazon Redshift Developer Guide. For more information on sort keys, see [Working with sort keys](https://docs.aws.amazon.com/redshift/latest/dg/t_Sorting_data.html). +_Migrating for tables with interleaved sort keys_ – When migrating Amazon Redshift provisioned clusters to Amazon Redshift Serverless, Redshift converts tables with interleaved sort keys and DISTSTYLE KEY to compound sort keys. The DISTSTYLE doesn't change. For more information on distribution styles, see [Working with data distribution styles](https://docs.aws.amazon.com//redshift/latest/dg/t_Distributing_data.html) in the Amazon Redshift Developer Guide. For more information on sort keys, see [Working with sort keys](https://docs.aws.amazon.com//redshift/latest/dg/t_Sorting_data.html).