Skip to main content
GET
Get egress-only gateway
Requires the IAM action network:GetEgressOnlyGateway. See NETWORK permissions for the full list, what each one covers, and an example policy.

Authorizations

Authorization
string
header
required

An OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. This is the recommended way to authenticate.

Get one by exchanging a service account's access key pair at POST /v1/oauth/token with grant_type=client_credentials. It is the standard client-credentials grant, so any OAuth-aware library will obtain and refresh it for you.

Tokens last an hour by default. The same access key pair is separately your AWS SigV4 credential for the S3-compatible object endpoint, which speaks nothing else.

Path Parameters

egress_only_gateway_id
string<uuid>
required

Egress-only Gateway ID

Response

Egress-only gateway details

egress_only_gateway
object

Native IPv6 egress without address translation: a subnet with global IPv6 whose route table points ::/0 at one gets OUTBOUND v6 (plus the return traffic of its own flows), but the internet can never initiate an inbound connection — a platform-band drop enforces that regardless of the tenant's security groups. It owns no address and does not translate ULA sources and reuses the VPC's internet gateway for the L3 uplink, so the VPC must have an IGW attached. One per VPC.