AWS redshift documentation change
Summary
Added connection pooling billing details and cost optimization recommendations
Security assessment
The changes focus on cost management aspects of connection pooling without addressing security controls or vulnerabilities. Recommendations are financial rather than security-focused.
Diff
diff --git a/redshift/latest/mgmt/serverless-billing.md b/redshift/latest/mgmt/serverless-billing.md index 388b34970..b06cf9262 100644 --- a//redshift/latest/mgmt/serverless-billing.md +++ b//redshift/latest/mgmt/serverless-billing.md @@ -5 +5 @@ -Billing for compute capacityBilling for storage Using the Amazon Redshift Serverless free trialBilling usage notes +Billing for compute capacityBilling for storage Using the Amazon Redshift Serverless free trialBilling usage notes Amazon Redshift Serverless billing with connection pooling @@ -69 +69 @@ Amazon Redshift Serverless offers a free trial. If you participate in the free t -The follwing are best practices and built-in settings that help keep your billing consistent. +The following are best practices and built-in settings that help keep your billing consistent. @@ -83,0 +84,23 @@ The follwing are best practices and built-in settings that help keep your billin +## Amazon Redshift Serverless billing with connection pooling + +Amazon Redshift Serverless treats all incoming queries as billable user activity, including lightweight health-check queries sent by connection pools. This behavior applies regardless of whether the query originates from an application, a JDBC/ODBC driver, or a connection pooling framework. Each health-check query triggers compute usage, and charges are incurred regardless of query purpose or origin. As a result, maintaining open connection pools can generate costs even when no actual user workloads are running. + +Connection pooling maintains a pool of persistent connections between applications and the Amazon Redshift Serverless endpoint. To ensure these connections remain healthy and available, pooling mechanisms often send lightweight or empty queries (for example, `SELECT 1`) at regular intervals. These automated queries verify connection status. + +When you use connection pooling, consider these best practices to minimize unintended charges: + + * Adjust health check frequency by reviewing and optimizing the frequency of health check or keep-alive queries in your connection pooling configuration. + + * Optimize idle system settings by configuring connection pooling to minimize unnecessary connection churn or background query activity during system idle times. + + * Implement application-level pooling or improved connection lifecycle management if it can reduce overhead. + + * Disable heartbeat or validation queries if your connection pooling configuration allows it. Check your specific connection string parameters or configuration files to adjust these settings. + + * Fine-tune TCP keepalive settings: If you can't disable the driver's internal heartbeat mechanisms, adjust Transmission Control Protocol (TCP) keepalive settings at the operating system or application level to address connection timeout issues. Refer to your operating system, JDBC/ODBC driver, or connection pool documentation for details. + + * Optimize database connection pooling: Configure your connection pool (HikariCP, Apache Database Connection Pool) to manage connections and minimize connection overhead. Focus on parameters such as maximum connections, idle timeout, and validation queries (if necessary). This optimization helps align Amazon Redshift Serverless compute usage with actual workload demand, potentially reducing costs. + + + +