Hello everyone, I'm planning to configure Amazon RDS Proxy for our standard RDS PostgreSQL setup, which consists of a single primary DB instance and one read replica. This setup is a Multi-AZ DB instance deployment, not a Multi-AZ DB cluster. According to AWS documentation, RDS Proxy supports read-only (reader) endpoints exclusively for Aurora clusters and Multi-AZ DB clusters. This implies that, for our non-Aurora RDS PostgreSQL configuration, we cannot create a reader endpoint through RDS Proxy. Consequently, our read replica wouldn't be able to handle read traffic via the proxy. Has anyone encountered a similar scenario? I'm interested in strategies to utilize RDS Proxy while directing read/write traffic to the primary instance and read-only traffic to the read replica. Specifically: • Is it feasible to configure RDS Proxy to route read-only traffic to a read replica in a non-Aurora RDS PostgreSQL setup? • Are there alternative methods or best practices to achieve read/write splitting in this context? Any insights or experiences you can share would be greatly appreciated.

Sorry, I don't understand why you aren't connecting the read-only reader to the read replica, and the other client to the regular DB instance. RDS Proxy is normally used when you need a connection pool, like when a Lambda needs access to the DB. But maybe I just don't understand the scenario completely.

with my current setup (single primary + read replica, non-Aurora, Multi-AZ instance), It seems RDS Proxy cannot be used to route read-only traffic to the read replica. the functionality-using RDS Proxy read-only endpoints to direct traffic to replicas-is only available for Aurora clusters and Multi-AZ DB clusters, not for classic Multi-AZ RDS PostgreSQL deployments with read replicas https://repost.aws/questions/QURgpYNcQWQ32HmZ8lDLmS8w/rds-postgres-rds-proxy-read-replicas so with my current set up even if i have a replica in place i cant route the traffic to that using the rds proxy