AWS AmazonRDS documentation change
Summary
Added notes to five CloudWatch metrics (QueryDatabaseResponseLatency, QueryRequests, QueryRequestsNoTLS, QueryRequestsTLS, QueryResponseLatency) clarifying that they do not include data for PostgreSQL workloads using Extended Protocol.
Security assessment
The change adds a clarification about metric coverage limitations for PostgreSQL Extended Protocol. This is a documentation update about monitoring scope, not a security fix. While one metric (QueryRequestsNoTLS) relates to non-encrypted connections, the change doesn't address any vulnerability or weakness; it only clarifies what data is excluded from monitoring.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/rds-proxy.monitoring.md b/AmazonRDS/latest/AuroraUserGuide/rds-proxy.monitoring.md index a31e56103..b2bef2000 100644 --- a//AmazonRDS/latest/AuroraUserGuide/rds-proxy.monitoring.md +++ b//AmazonRDS/latest/AuroraUserGuide/rds-proxy.monitoring.md @@ -58,5 +58,5 @@ Metric | Description | Valid period | CloudWatch dimension set -`QueryDatabaseResponseLatency` | The time in microseconds that the database took to respond to the query. The most useful statistic for this metric is `Average`. | 1 minute and above | Dimension set 1, Dimension set 2, Dimension set 3, Dimension set 4 -`QueryRequests` | The number of queries received. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. | 1 minute and above | Dimension set 1, Dimension set 2 -`QueryRequestsNoTLS` | The number of queries received from non-TLS connections. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. | 1 minute and above | Dimension set 1, Dimension set 2 -`QueryRequestsTLS` | The number of queries received from TLS connections. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. | 1 minute and above | Dimension set 1, Dimension set 2 -`QueryResponseLatency` | The time in microseconds between getting a query request and the proxy responding to it. The most useful statistic for this metric is `Average`. | 1 minute and above | Dimension set 1, Dimension set 2 +`QueryDatabaseResponseLatency` | The time in microseconds that the database took to respond to the query. The most useful statistic for this metric is `Average`. **Note:** Does not include data for PostgreSQL workload using Extended Protocol. | 1 minute and above | Dimension set 1, Dimension set 2, Dimension set 3, Dimension set 4 +`QueryRequests` | The number of queries received. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. **Note:** Does not include data for PostgreSQL workload using Extended Protocol. | 1 minute and above | Dimension set 1, Dimension set 2 +`QueryRequestsNoTLS` | The number of queries received from non-TLS connections. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. **Note:** Does not include data for PostgreSQL workload using Extended Protocol. | 1 minute and above | Dimension set 1, Dimension set 2 +`QueryRequestsTLS` | The number of queries received from TLS connections. A query including multiple statements is counted as one query. The most useful statistic for this metric is `Sum`. **Note:** Does not include data for PostgreSQL workload using Extended Protocol. | 1 minute and above | Dimension set 1, Dimension set 2 +`QueryResponseLatency` | The time in microseconds between getting a query request and the proxy responding to it. The most useful statistic for this metric is `Average`. **Note:** Does not include data for PostgreSQL workload using Extended Protocol. | 1 minute and above | Dimension set 1, Dimension set 2