Today we're launching Supabase PrivateLink, a new capability that lets you connect your database to AWS cloud resources over private networks. When enabled, your database connections stay entirely within the AWS network. No public internet exposure. No additional attack surface.
If you work in a regulated industry or handle sensitive data, you've had this conversation with your security team: "Can we connect to the database without going over the public internet?" Until now, the answer was complicated. You could use IP allowlists and SSL, but traffic still flowed over public networks. For some organizations, that's a non-starter.
Supabase PrivateLink solves this. Traffic never leaves private networks. From a network perspective, your Supabase database behaves like it's inside your own VPC.
This matters for compliance. Many regulatory frameworks require private network connectivity for sensitive data. It also matters for security. Fewer public endpoints mean fewer attack vectors. You can disable public database access entirely once PrivateLink is configured.
Our AWS PrivateLink implementation uses AWS VPC Lattice under the hood. When you enable PrivateLink, we share a VPC Lattice Resource Configuration with your AWS account. You accept the share and create an endpoint in your VPC.
