Hey AWS / Postgres folks — running into a tricky situation.Clients currently connect directly to my RDS Postgres endpoint using the usual host/user/password. But now I need every connection to first pass through an EC2 instance where my agent runs (for auditing/filtering), and then that agent should forward the connection to the actual RDS.The challenge is that this needs to be completely transparent. Clients shouldn’t change their connection string, shouldn’t see a different endpoint, and shouldn’t know anything changed.Has anyone implemented something like this before? Maybe using HAProxy or PgBouncer on EC2, Route53 tricks, NLB, or some VPC routing setup? #AWS #PostgreSQL #DevOps
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)