Private networking with AWS PrivateLink
With AWS PrivateLink, Weld reaches your database over the AWS network instead of the public internet. Your database doesn't need a public address, an IP allowlist or an SSH bastion.
Private networking is available on the Enterprise plan, on request. Talk to us to set it up.
How it works
- Weld's sync workers run in Weld's AWS account.
- We create a VPC endpoint for your workspace in Weld's AWS account, in the same AWS region as your database.
- In your AWS account, you share the database with Weld's AWS account, as a VPC Lattice resource configuration or a VPC endpoint service.
- The endpoint and your database talk over AWS PrivateLink, so the traffic stays on the AWS network.
- Weld only connects to private addresses through your workspace's own endpoint, never another workspace's.
Supported databases
- PostgreSQL
- MySQL
- SQL Server
The database has to run in AWS, for example on Amazon RDS, Amazon Aurora or EC2. For another source, ask us.
Regions
Weld connects to your database from an endpoint in the same AWS region, so we create the endpoint in your database's region. Weld runs endpoints in:
| Region | Code |
|---|---|
| Europe (Frankfurt) | eu-central-1 |
| US East (N. Virginia) | us-east-1 |
If your database is in another region, talk to us.
Set it up
- Contact us with the region and the databases you want to connect. We send you Weld's AWS account ID.
- Share your database with that account, in one of two ways:
- VPC Lattice resource configuration (recommended): create a resource gateway and a resource configuration that points at your database's endpoint name, then share it with Weld's AWS account through AWS Resource Access Manager (RAM). Because it points at the endpoint name, failovers keep working.
- VPC endpoint service: put a Network Load Balancer in front of the database, create an endpoint service and allow Weld's AWS account. The load balancer's targets have to follow the database's IP addresses, which can change on failover, so an RDS Proxy in front of the database helps.
- We create the endpoint, link it to your workspace and send you its host name.
- Connect the database in Weld as usual, and use that host name as the host. Port, user and password stay the same.
Good to know
- If your database requires certificate host name verification, tell us when you set it up, because the endpoint's host name differs from the name on the database's certificate.
- SSH tunnels stay available on every plan if you'd rather use a bastion host.
- For running Weld's workers in a dedicated environment or in your own AWS account, see Deployment options.