Database
CoreAmazon RDS Proxy
Explicit RDS performance-efficiency example and connection-management boundary.
Key points
- RDS Proxy addresses supported connection pooling and churn rather than query or storage performance.
Best-known use cases
- D1.3, D2.1, and D2.2: place supported clients behind RDS Proxy when connection pressure is the measured bottleneck.
What candidates often confuse it with
- RDS Proxy manages database connections; RDS instance, storage, read, and query controls address other pressure.
Key takeaway
Choose RDS Proxy only after evidence separates connection exhaustion from slow queries or saturated resources.
Related services
- Amazon Aurora
- Amazon Aurora Serverless v2
- Amazon DynamoDB
Relevant exam tasks
- D1.3 — Task 1.3: Implement performance optimization strategies for compute, storage, and database resources.
- 1.3.1 — Optimize compute resources and remediate performance problems by using performance metrics, resource tags, and AWS tools.
- D2.1 — Task 2.1: Implement scalability and elasticity.
- 2.1.1 — Configure and manage scaling mechanisms in compute environments.
- D2.2 — Task 2.2: Implement highly available and resilient environments.
- 2.2.1 — Configure and troubleshoot Elastic Load Balancing (ELB) and Amazon Route 53 health checks.