Complementing amazon Web Services (AWS) amazon.com/rds/” rel=”noopener ugc nofollow” target=”_blank”>Relational database service (RDS), Proxy became amazon.com/about-aws/whats-new/2020/06/amazon-rds-proxy-generally-available/” rel=”noopener ugc nofollow” target=”_blank”>Generally available in June 2020 on RDS for MySQL and PostgreSQL, as well as their Aurora-compatible counterparts. Proxy facilitates pooling and sharing of database connections, which is valuable for serverless applications that need to query RDS databases at scale with managed failover. Since June 2020, Proxy has expanded support to RDS for MariaDB and SQL Server.
RDS Proxy already has excellent documentation: amazon.com/rds/proxy/” rel=”noopener ugc nofollow” target=”_blank”>amazon Product Documentation is a useful reading reference. This blog post builds on existing material and focuses on lessons learned when configuring and monitoring a proxy. These observations come from experience using Proxy with Aurora MySQL, but apply regardless of the target database engine.
There is amazon.com/AmazonRDS/latest/UserGuide/rds-proxy.howitworks.html” rel=”noopener ugc nofollow” target=”_blank”>Some Proxy Terms To explain before we dive into the lessons learned, first, database (DB) instances are called goals, and the targets are associated with a Proxy target groupEach target group consists of a single RDS DB instance or an RDS DB cluster, where a cluster has many DB instances. The proxy uses one or more end points to forward queries to target groups.
