Build Service Gateway route rule configurations for private access to OCI services.
Last verified: May 2026
Build Service Gateway route rule configurations for private access to OCI services from VCN subnets.
Required Fields
compartmentIdvcnIddisplayNameservicesOutput will appear here...Your team's VMs constantly upload to OCI Object Storage. Without a Service Gateway, this traffic egresses through the NAT Gateway — adding $0.045/GB processing fee plus internet routing latency. The builder generates: a Service Gateway with the all-services CIDR enabled, route table updates pointing the OCI services CIDR to the gateway. After deploy, Object Storage traffic stays on OCI's internal network (free + faster). For a workload doing 5 TB/month of uploads, that's $225/month in NAT processing fees eliminated.
Build Service Gateway route rule configurations for private access to OCI services. This tool helps OCI engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
The builder constructs OCI Service Gateway configurations: service gateway resource (compartment, VCN reference), service CIDR labels to enable (`all-<region>-services-in-oracle-services-network` for all OCI services, or specific service labels like `objectstorage` for narrow access), and route rules in the VCN's route tables directing service traffic to the gateway. Output is generated as oci network service-gateway commands and Terraform oci_core_service_gateway + oci_core_route_table resources.
Service Gateway is FREE — both the gateway resource and the data flowing through it. This is dramatically different from AWS PrivateLink (charges per VPC endpoint + data processed) or Azure Private Endpoint. Always use Service Gateway for VCN-to-OCI-services traffic; never route via the public internet.
Service Gateway routes traffic to OCI services WITHIN the same region. For cross-region access (e.g., Object Storage in another region), traffic uses the public internet unless you set up FastConnect public peering. Plan your service access architecture accordingly.
Add Service Gateway routes for Object Storage by default in every production VCN. Without it, Object Storage uploads/downloads from your VMs traverse the internet path — adding latency and exposing data to public internet routing. The Service Gateway path is private + faster.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.