Limits on Resources Provided by Compute Cloud@Customer

Review the limits on the resources provided to customers by a Compute Cloud@Customer infrastructure.

Resource Limits per Infrastructure

The numbers provided here apply to any Compute Cloud@Customer infrastructure, regardless of its hardware configuration.

Service

Resource Type

Limit

Networking Service

VCNs

80

Networking Service

Subnets

40 per VCN

Networking Service

Dynamic routing gateways

1 per VCN

Networking Service

Internet gateways

1 per VCN

Networking Service

Local peering gateways

5 per VCN

Networking Service

NAT gateways

1 per VCN

Networking Service

Service gateways

1 per VCN

Networking Service

Reserved public IPs

The range specified on the Compute Cloud@Customer Network Spreadsheet

Networking Service

Ephemeral public IPs

2 per compute instance

Networking Service

DHCP options

30 per VCN

Networking Service

Route tables

20 per VCN

Networking Service

Route rules

50 per route table

Networking Service

Network security groups

100 per VCN

Networking Service

VNICs in network security group

As many VNICs as are in the VCN.

A VNIC can belong to max. 5 network security groups

Networking Service

Security rules

50 per network security group

Networking Service

Security lists

20 per VCN

5 per subnet

Networking Service

Ingress rules

30 per security list

Networking Service

Egress rules

30 per security list

Networking Service

DNS zones 1000 (in addition to any internal zones)

Networking Service

DNS records 25000 per zone

Compute Service

Custom images

100

Block Storage Service

Aggregated size of block volumes

100 TB (with default storage capacity)

Block Storage Service

Block volume backups

100000

File Storage Service

File systems

100

File Storage Service

Mount targets

10

File Storage Service

File system size

3.3 PB

Object Storage Service

Buckets

10000

(Network) Load Balancing Service

Load balancers (Network LB and LBaaS combined)

24 total across all tenancies, 20 in a single VCN

(Network) Load Balancing Service

IP address

1 per load balancer

(Network) Load Balancing Service

Network security groups

5 per load balancer

(Network) Load Balancing Service

Listeners

16 per load balancer

(Network) Load Balancing Service

Backend sets

4 per load balancer

(Network) Load Balancing Service

Backend servers

512 per load balancer and per backend set

OKE service

Clusters

20 per tenancy

OKE service

Worker nodes

128 per cluster (across all pools)

OKE service

Nodes per node pool/group

128

OKE service

Pods

110 per node (Kubernetes default)