Networking
Open and close ports, give an instance its own IPv4 address, and serve your own domain over TLS.
Every instance is closed to the internet except for the ports you open. Inbound traffic to anything else is dropped, and outbound traffic is open to the internet but closed to the platform's hosts, its internal networks and other tenants.
Endpoints
Each open port is an endpoint in the instance's endpoints:
"endpoints": [
{ "name": "ssh", "host": "51.81.170.114", "ipVersion": "ipv4", "port": 10443 },
{ "name": "attest", "host": "51.81.170.114", "ipVersion": "ipv4", "port": 5699 }
]Endpoints are assigned when the create is accepted and never change while the rules stay the same. Always read the host and port from endpoints; never assume the guest's own port number.
With the general-purpose image, the image's attestation port is always published as the endpoint named attest; do not list it in ingress. See Verify an instance.
Shared or dedicated IPv4
network.publicIp | Inbound | Outbound |
|---|---|---|
shared (default) | Your ports are mapped to ports the platform picks on a shared IPv4 address in the instance's location | Leaves from the shared address with standard SNAT |
dedicated | The instance's own IPv4 address, on the guest's own port numbers | Leaves from the instance's own address |
Choose dedicated at create, where the location's publicIpModes includes it, or add and remove it later without recreating the instance:
# Give a running instance its own IPv4 address
curl -X POST https://api.cloud.confidential.ai/v1/instances/$ID/dedicated-ipv4 \
-H "Authorization: Bearer $CC_API_KEY" -H "Api-Version: 2026-10-15" \
-H "Idempotency-Key: $(uuidgen)"
# Return it to the shared address
curl -X DELETE https://api.cloud.confidential.ai/v1/instances/$ID/dedicated-ipv4 \
-H "Authorization: Bearer $CC_API_KEY" -H "Api-Version: 2026-10-15"Both return 202 while the change is applied, then 200 once it is done. While network.ipv4Transition is present (waiting, adding or removing), the change is still in progress; existing connections may need to reconnect, and you should use the endpoints the response returns. A request still waiting for a free address can be cancelled with the DELETE. An instance that is not on a host yet returns 409 invalid_state: add the address once it is running. When the address is removed or the instance deleted, it returns to the pool and may later be assigned to another customer.
Open and close ports
Open ports at create in network.ingress, or on a running instance at any time:
curl -X POST https://api.cloud.confidential.ai/v1/instances/$ID/ingress \
-H "Authorization: Bearer $CC_API_KEY" -H "Api-Version: 2026-10-15" \
-H "Idempotency-Key: $(uuidgen)" -H "Content-Type: application/json" \
-d '{ "name": "web", "port": 8080 }'The response is 202 with the instance. It already lists the rule in network.ingress and its new endpoint in endpoints, such as { "name": "web", "host": "51.81.170.114", "port": 7262 }, and network.ingressUpdating is true until the location has applied the change. Connect once it is absent. Adding a rule never changes the instance's address, its other endpoints or any open connection.
Close a port by its name:
curl -X DELETE https://api.cloud.confidential.ai/v1/instances/$ID/ingress/web \
-H "Authorization: Bearer $CC_API_KEY" -H "Api-Version: 2026-10-15"Connections on that port end; other ports are unaffected.
Rules are TCP only, at most 16 per instance, each with a unique name (lowercase letters, digits and -, up to 15 characters) and a unique port. A name or port another rule uses returns 409 name_conflict, and a shared address with no free port returns 409 insufficient_capacity.
In the console, open an instance and use its Open ports section to add or remove rules. Its Custom domains section registers and verifies your own hostnames.
Hostnames
In a location that names instances, every instance gets a hostname under the location's hostnameDomain, listed in network.hostnames:
i-9pj5dy9i6cbu.hil1.compute.confidential.aiA rule on port 443 also opens the hostname on port 443. TLS connections to it reach the guest's port 443 as the client sent them: the platform routes by the TLS server name and never ends TLS, so the guest holds its own certificate and private key.
Your own domain
To serve shop.example.com from an instance, register it, prove you own it with a TXT record, then point it at the instance:
# 1. Register the hostname; the response carries the TXT record to publish
curl -X POST https://api.cloud.confidential.ai/v1/instances/$ID/domains \
-H "Authorization: Bearer $CC_API_KEY" -H "Api-Version: 2026-10-15" \
-H "Idempotency-Key: $(uuidgen)" -H "Content-Type: application/json" \
-d '{ "hostname": "shop.example.com" }'
# 2. Publish the TXT record from the response's verification, then verify
curl -X POST https://api.cloud.confidential.ai/v1/instances/$ID/domains/$DOMAIN_ID/verify \
-H "Authorization: Bearer $CC_API_KEY" -H "Api-Version: 2026-10-15" \
-H "Idempotency-Key: $(uuidgen)"- Point the hostname at the instance's managed hostname with a CNAME, or at the location's gateway address for an apex domain.
The instance needs a managed hostname and port 443 open. A CNAME alone never routes a name to an instance; only a verified registration does. A verified name stays reserved to your organization even after you remove it. To move a name to another instance in your organization, register and verify it there with ?replaceDomainId=<old registration id>, which switches the route in one step. Deleting an instance cancels its registrations.
Encrypt inside the guest
The platform's hosts carry every packet an instance sends or receives, in the clear wherever the guest does not encrypt it. Use TLS, SSH or another protocol that encrypts inside the guest for anything secret, and terminate it in the guest, never in front of it.
What is not offered yet
- Private networks between your instances: locations return
privateNetworks: false, andnetwork.privateNetworkreturns422 unsupported_combination. - IPv6: where a location's
ipv6istrue, instances also get their own IPv6 address with the same ports open on the guest's own port numbers. No location routes IPv6 yet. - Fixed outbound source ports or connection counts: shared outbound uses standard SNAT with dynamically chosen source ports. Reuse connections where you can.