AWS redshift documentation change
Summary
Updated documentation about version update processes for Redshift Serverless workgroups, changing update timing from 'during idle periods' to 'immediately' and revised trailing track explanation
Security assessment
Changes focus on operational update processes and testing workflows rather than addressing security vulnerabilities. No security-specific terminology or mitigations were added.
Diff
diff --git a/redshift/latest/mgmt/tracks.md b/redshift/latest/mgmt/tracks.md index af7a84518..373cf3a6d 100644 --- a//redshift/latest/mgmt/tracks.md +++ b//redshift/latest/mgmt/tracks.md @@ -11 +11 @@ When Amazon Redshift releases a new version, it updates the version of your Amaz -The serverless workgroup or provisioned cluster's track determines which released version is applied during a version update. Amazon Redshift updates provisioned clusters during the specified maintenance window. For serverless workgroups, updates are online and seamless, without a set maintenance window. Amazon Redshift determines the timing of serverless workgroup updates based on activity levels, applying the update during idle periods or times of low activity. When Amazon Redshift releases a new version, that version is assigned to the _current_ track, and the previous version is assigned to the _trailing_ track. To set the track for your data warehouse, specify one of the following values: +The serverless workgroup or provisioned cluster's track determines which released version is applied during a version update. Amazon Redshift updates provisioned clusters during the specified maintenance window, and updates serverless workgroups immediately. When Amazon Redshift releases a new version, that version is assigned to the _current_ track, and the previous version is assigned to the _trailing_ track. To set the track for your data warehouse, specify one of the following values: @@ -22 +22 @@ For example, suppose that your serverless workgroup is currently running version -For Redshift Serverless workgroups, you have the option to run a subset of Redshift Serverless workgroups in the Redshift Serverless Trailing track. This allows for 1-6 weeks of testing and integration validation in your environment before adopting the release across all of your workgroups. By default, Redshift Serverless creates all workgroups in the Current track to take advantage of the most up-to-date, certified release. Redshift Serverless Trailing track gives you additional diligence and time needed for testing and development environments to evaluate the Current track before adopting the Current track for your mission-critical workloads in production. The Trailing track ensures maximum stability, making it ideal for mission-critical workloads in production environments. +With the trailing track feature, you have the option to run a subset of Amazon Redshift data warehouses in the trailing track. This allows for 1-6 weeks of testing and integration validation on data warehouses set to the Current track before appying the release to data warehouses on the Trailing track. By default, Amazon Redshift creates all clusters and workgroups on the Current track to take advantage of the most up-to-date, certified relesase. However, using the Amazon Redshift trailing track in your production environment, and the current track in your testing and development environment, gives you additional diligence and time to evaluate the latest release. The Trailing track ensures maximum stability, making it ideal for mission-critical workloads in production environments.