AWS redshift: Clarify Redshift Serverless Max capacity vs RPU hour limits wording
Summary
Rewords cost-control explanations distinguishing Max capacity from maximum RPU hour limits, fixes a typo (compliment->complement), removes a note about Max capacity not interfering with queries, and adds a new note that lowering Max capacity below current base capacity immediately reduces capacity and can affect running workloads.
Security assessment
The changes are editorial/cost-management and operational-behavior clarifications about RPU capacity scaling; the added note warns of immediate capacity reduction affecting running workloads, which is an availability/performance consideration, not a documented security control or vulnerability fix.
Evidence
+ * Max capacity changes usually do not disrupt running queries. However, if you set Max capacity below your current base capacity, Amazon Redshift Serverless will immediately reduce capacity. This can affect your running workload.
Diff
diff --git a/redshift/latest/mgmt/serverless-billing-on-demand.md b/redshift/latest/mgmt/serverless-billing-on-demand.md index 987fcb027..487206628 100644 --- a//redshift/latest/mgmt/serverless-billing-on-demand.md +++ b//redshift/latest/mgmt/serverless-billing-on-demand.md @@ -52 +52 @@ The Max capacity setting serves as the RPU ceiling that Amazon Redshift Serverle -The purpose of both maximum RPU hour limits and the Max capacity setting is to control cost. But they achieve this through different means. The following points explain the difference: +Both maximum RPU hour limits and Max capacity can help you control cost, but they work in different ways. The following points explain the difference: @@ -54 +54 @@ The purpose of both maximum RPU hour limits and the Max capacity setting is to c - * _Max capacity_ – This setting establishes the highest count of RPUs that Amazon Redshift Serverless uses for scaling purposes. When automatic compute scaling is required, having a higher value for Max capacity can enhance query throughput. When the Max capacity limit is reached, the workgroup doesn't scale up resources any further. + * _Max capacity_ – This setting establishes the highest count of RPUs that Amazon Redshift Serverless can use for automatic scaling purposes. @@ -61 +61 @@ The purpose of both maximum RPU hour limits and the Max capacity setting is to c -You can use Max capacity exclusively, or you can compliment it with actions from maximum RPU hour usage limits. +You can use Max capacity exclusively, or you can complement it with actions from maximum RPU hour usage limits. @@ -84 +84,3 @@ These notes can help you set Max capacity appropriately: - * Configuring the Max capacity setting doesn't interfere with running queries, even during times of high RPU usage. It doesn't work like a usage limit, which can stop queries from running. It only limits compute resources available to the workgroup. You can view capacity used over a period of time on the Amazon Redshift Serverless dashboard. For more information about viewing summary data, see [Checking Amazon Redshift Serverless summary data using the dashboard](https://docs.aws.amazon.com/redshift/latest/mgmt/serverless-dashboard.html). + * You can view capacity used over a period of time on the Amazon Redshift Serverless dashboard. For more information about viewing summary data, see [Checking Amazon Redshift Serverless summary data using the dashboard](https://docs.aws.amazon.com/redshift/latest/mgmt/serverless-dashboard.html). + + * Max capacity changes usually do not disrupt running queries. However, if you set Max capacity below your current base capacity, Amazon Redshift Serverless will immediately reduce capacity. This can affect your running workload.