Each revision has an egress mode. Requests reach your service whichever mode it has.
| Mode | Its code reaches |
|---|---|
internet (default) |
The internet, from shared addresses, as a sandbox does |
vpc |
A subnet of a VPC in the service’s project |
none |
Nothing, EZGH APIs included |
A VPC
{ "egress": { "mode": "vpc", "vpc": { "subnet": "sbn_7hq2m0x9ka3c" } } }- The subnet must be in the service’s project, and the caller needs
network.subnets.geton it. - Instances get addresses in the subnet and reach the internet only through a NAT gateway in the VPC, IPv4 only, as a sandbox in a VPC does.
ezgh run deploy api --image <id>.registry.ezghcloud.com/acme/api:2 --egress vpc --subnet sbn_7hq2m0x9ka3cNone
An instance has no network at all: it can’t make a connection, to the internet or to EZGH. It still serves requests.