Modifying RDS Configurations With Performance Insights and RDS Proxy

​

Amazon RDS Performance Insights — overview and value

• Visualization of DB load (DB load) and wait categories to show where time is spent.
• Top SQL: identify long-running queries or queries using the most CPU/IO.
• Historical and near-real-time analysis to compare trends and seasonality.
• Actionable recommendations: instance sizing, parameter group adjustments, indexing, and query tuning.

SELECT SUM(order_amount) FROM orders WHERE order_status = 'Pending';

SELECT * FROM customers ORDER BY last_name;

SELECT * FROM customers WHERE email LIKE '%gmail.com';

• Increase instance size if CPU, memory, or I/O are constraining throughput.
• Tune parameter groups (cache sizes, buffer pool settings, timeouts).
• Add or change indexes and rewrite queries to avoid full table scans.

• On transactional systems (for example, e‑commerce checkouts), addressing inefficient queries and adding appropriate indexes often reduces latency and DB load substantially — improvements of tens of percent are common depending on the root cause.

# Example: enable Performance Insights when creating a DB instance
aws rds create-db-instance \
  --db-instance-identifier mydb \
  --db-instance-class db.t3.medium \
  --engine mysql \
  --allocated-storage 20 \
  --enable-performance-insights

​

RDS Proxy — connection management and resilience

• Connection pooling and reuse: reduces total concurrent DB connections and connection churn.
• Improved scalability: smooths bursts of connection requests from many short-lived clients (e.g., serverless functions).
• Reduced failover impact: during Multi‑AZ failover, the proxy can manage reconnections and reduce visible disruption.
• Security integration: supports AWS Secrets Manager and IAM authentication for supported engines.

• Applications connect to the proxy endpoint.
• The proxy keeps a pool of persistent backend DB connections.
• The proxy hands out connections from that pool instead of creating new DB connections per client request.
• During failover, the proxy can transparently reconnect and route traffic to the new primary, minimizing client-side errors.

• Use Performance Insights to find top resource consumers and to guide indexing and parameter changes.
• Use RDS Proxy for workloads that create many short-lived connections (serverless functions, lambda-based backends) or to minimize failover impact in Multi‑AZ setups.
• Both features are commonly referenced in AWS exams for database monitoring, scaling, and resilience scenarios.

​

Links and references

• Performance Insights docs: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PerfInsights.html
• RDS Proxy docs: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-proxy.html
• AWS RDS CLI reference: https://docs.aws.amazon.com/cli/latest/reference/rds/index.html