The latest articles on DEV Community by Rohan Patil (@rohan_patil_8ccd886e1dda9). https://dev.to/rohan_patil_8ccd886e1dda9 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3596623%2Fd934f6aa-ebcb-44b5-b3eb-06049d96e6f3.png https://dev.to/rohan_patil_8ccd886e1dda9 en Rohan Patil Fri, 13 Mar 2026 12:37:38 +0000 https://dev.to/rohan_patil_8ccd886e1dda9/need-help-aws-level-2m3l https://dev.to/rohan_patil_8ccd886e1dda9/need-help-aws-level-2m3l <p>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</p> networking aws database techtalks