Quickstart
This walks through the smallest useful deployment: two connectors, one published service, one policy. Fifteen minutes if your egress is already open.
The endpoint names below are provisional.
api.proxility.scailabs.aiand*.edge.proxility.scailabs.aido not resolve yet — the control plane is not generally available (see the status table on Proxility). Nobody should spend an afternoon debugging DNS for a service that has not launched. Correct these names here the moment the real ones exist.
Before you start#
- A Proxility tenant and a realm. If you have neither, ask your administrator or see Tenants and realms.
- Two networks, each with a Linux host that has outbound access to
*.edge.proxility.scailabs.aion UDP/443 (TCP/443 is the fallback). - The
proxilityCLI on your workstation.
1 2 3 | |
1. Install the connector in the first network#
On the host inside your data centre:
1 2 3 | |
Then on the host:
1 2 3 | |
The connector generates its own keypair during enrolment. The private key never leaves the host — the token only proves the host is allowed to ask for a certificate. Check in:
1 2 3 | |
2. Install the connector in the second network#
Same two steps, different name:
1 2 3 | |
3. Publish a service#
Services are published by the connector that can reach them locally:
1 2 3 4 | |
That service is now named payments.prod.acme.prox. It is not yet reachable
by anyone.
4. Allow one thing#
Default deny means nothing happens until you say so:
1 2 3 4 5 | |
5. Use it#
From the cloud host:
1 | |
Name resolution happens inside the connector's split-horizon resolver; see Services and DNS. The TLS session your client negotiates is your own, end to end to the target — Proxility's encryption is underneath it and does not terminate yours.
6. Watch the decision#
1 2 | |
A denied attempt looks like this, and names the absence of a rule rather than failing silently:
1 | |
What to read next#
- Policy — how rules are written and evaluated, and why they are checked twice
- Connect a network — production deployment: redundant connectors, sizing, upgrades
- Cryptography — what actually protects the session