Planning Resource Limit Settings
The tables in this topic show the maximum allowable limit for each resource and tag.
Important:
You might not be able to set a limit override to the maximum allowable value. The limit you can set depends on other configuration, including limit overrides that you have already set for related resources.
If creating a limit override fails because you have attempted to set the limit too high, you will receive an error message with information about why the limit is too high and what the limit can be. Using this information, you might decide to override a different limit as well as, or instead of, the limit you were attempting to override.
In the following example, the maximum value for load-balancers is 12, and the user attempts to set a new value of 14.
PCA-ADMIN> create LimitOverride serviceName=loadbalancer limitName=load-balancers value=14 tag=SYSTEM
Command: create LimitOverride serviceName=loadbalancer limitName=load-balancers value=14 tag=SYSTEM
Status: Failure
Time: 2025-05-06 18:08:33,621 UTC
Error Msg: PCA_GENERAL_000037: Error returned from Limit service. Code: 'InvalidParameter'.
Message: 'Rule 'lb' violated: {loadbalancer/load-balancers} <= 12'Some of the limits in the following tables do not show a range in the Allowable Limit column. They show the same value in the Allowable Limit column that they show in the Default Limit column. These limit values cannot be overridden.
PCA-ADMIN> create LimitOverride serviceName=network limitName=subnet-count tag=SYSTEM value=30 Command: create LimitOverride serviceName=network limitName=subnet-count tag=SYSTEM value=30 Status: Failure Time: 2025-05-06 18:34:16,008 UTC Error Msg: PCA_GENERAL_000037: Error returned from Limit service. Code: 'NotSupportedError'. Message: 'Limit 'network/subnet-count' does not support overrides.'
Use the procedures described in Listing and Showing Limit Definitions with the service names and limit names shown in the following tables to get additional information such as the limit description and supported tags.
File System Limits
All Filesystem service limits have service name file-system.
The maximum allowable limit might not be possible in your environment. See the Important note at the beginning of this topic.
Table 5-1 Filesystem Service Limits
| Limit Name | Default Limit | Allowable Limit |
|---|---|---|
| file-system-count | 800 | 0 - 800 |
| file-system-sys-count | 800 | 0 - 800 |
| mount-target-count | 80 | 0 - 80 |
| mount-target-sys-count | 80 | 0 - 80 |
IAM Service Limits
All IAM service limits have service name identity.
The maximum allowable limit might not be possible in your environment. See the Important note at the beginning of this topic.
Table 5-2 IAM Service Limits
| Limit Name | Default Limit | Allowable Limit |
|---|---|---|
| users | 100 | 0 - 800 |
| groups | 100 | 0 - 800 |
| dynamic groups | 50 | 0 - 400 |
| compartments | 50 | 0 - 400 |
| policies | 100 | 0 - 800 |
| policy-statements | 50 | 0 - 400 |
| group-users | 100 | 0 - 800 |
| user-groups | 100 | 0 - 800 |
| idps | 3 | 0 - 24 |
| idp-group-mappings | 100 | 0 - 800 |
| tag-namespaces | 100 | 0 - 800 |
| tags | 100 | 0 - 800 |
| tag-defaults | 5 | 0 - 40 |
| cost-tracking-tags | 10 | 0 - 80 |
| api-keys | 3 | 0 - 24 |
Load Balancer Service Limits
All Load Balancer service limits have service name loadbalancer and tag
SYSTEM.
The maximum allowable limit might not be possible in your environment. See the Important note at the beginning of this topic.
Table 5-3 Load Balancer Service Limits
| Limit Name | Default Limit | Maximum Allowable Limit |
|---|---|---|
| listeners | 16 | 0 - 16 |
| backend-sets | 16 | 0 - 16 |
| backends | 512 | 0 - 512 |
| hostnames | 4 | 0 - 4 |
| path-route-sets | 16 | 0 - 16 |
| network-security-groups | 5 | 0 - 5 |
| certificates | 16 | 0 - 16 |
| cipher-suites | 16 | 0 - 16 |
| load-balancers | 12 | 0 - 12 |
| load-balancers-min-total | 36 | 36 |
| load-balancers-total | 144 | 0 - 144 |
Note that the load-balancers-min-total limit cannot be overridden. The
limit value of load-balancers-min-total can only be 36. The only exception
is if you assign a template to SYSTEM with no limit value set for
load-balancers-min-total and defaultValueBehavior set to
ZERO.
You can set load-balancers-total as high as 144, but the effective limit
depends on how many compute nodes the system has. For example, if you have six compute
nodes, the effective load-balancers-total is 72, even if you set the limit
higher.
Network Limits
All Network service limits have service name network.
The maximum allowable limit might not be possible in your environment. See the Important note at the beginning of this topic.
Table 5-4 Network Service Limits
| Limit Name | Default Limit | Allowable Limit |
|---|---|---|
| vcn-system-count | 80 | 80 |
| subnet-system-count | 320 | 320 |
| subnet-count | 40 | 40 |
| vcn-count | 80 | 0 - vcn-system-count |
| nsg-count | 100 | 0 - 100 |
| nsg-rule-count | 50 | 0 - 300 |
Storage Controller Limits
All Storage Controller service limits have service name block-storage and
tag SYSTEM.
The maximum allowable limit might not be possible in your environment. See the Important note at the beginning of this topic.
Table 5-5 Storage Controller Service Limits
| Limit Name | Default Limit | Allowable Limit |
|---|---|---|
| volume-count | 32 | 0 - 32 |
| vol-group-volume-count | 32 | 0 - 32 |