When and Why to Use PrivateLink
Use PrivateLink when your Autonomy Agent needs to connect to any non-public system, such as:- A PostgreSQL instance in a private AWS VPC
- An internal microservice only accessible on a corporate network
- A legacy ERP system in a datacenter
- A developer’s laptop running a preview environment
How It Works
You run a lightweight Autonomy relay (called a “remote worker”) on or near your private resource. The remote worker registers a route to the private service (e.g., localhost:5432 for a database). Your Autonomy Agent requests a PrivateLink to that service. Autonomy brokers a mutually authenticated, encrypted tunnel from the Agent to the private service via the relay. The Agent receives a local port to connect to (e.g., localhost:7000), and from its point of view, the service “just works.” No changes are required to your network. The private service doesn’t need to listen on a public port. Everything is encrypted and access-controlled using cryptographic identities and short-lived credentials.autonomy.yaml
images/main/main.py