When you sign up for Oracle Cloud Infrastructure, a set of service limits is configured for your tenancy. The service limit is the quota or allowance set on a resource. For example, a tenancy is allotted a maximum number of compute instances per availability domain. These limits are established with the Oracle sales representative when you buy Oracle Cloud Infrastructure. If you didn't establish limits with the Oracle sales representative, or, if you signed up through the Oracle Store, default or trial limits are set for your tenancy. These limits might be increased for you automatically based on your Oracle Cloud Infrastructure resource usage and account standing. You can also request a service limit increase.
Depending on whether you have a subscription, you can view the limits and usage for it. The same service can have two different limit values, depending on which subscription you have selected on the Limits, Quotas and Usage page. Some services aren't tied to any subscription, but still have limit values associated with them. For more information, see Viewing a Tenancy's Limits and Usage (By Region).
Compartment Quotas 🔗
Compartment quotas are similar to service limits; the biggest difference is that service limits are set by Oracle, and compartment quotas are set by administrators, using policies that allow them to allocate resources with a high level of flexibility. Compartment quotas are set using policy statements written in a declarative language that's similar to the IAM policy language.
You can view a tenancy's limits, quotas, and usage in the Console. Be aware that:
The Console might not display limits and usage information for all the Oracle Cloud Infrastructure services or resources.
The usage level listed for a particular resource type could be greater than the limit if the limit was reduced after the resources were created.
If all the resource limits are listed as 0, this means your account has been suspended. For help, contact Oracle Support.
If you don't yet have a tenancy or a user account for the Console, or if you don't find a particular limit listed in the Console, see
Limits by Service for the default tenancy limits.
Service Limits API Policy 🔗
For the resource availability API (usage) the policy can be at the tenant or compartment level:
Allow group LimitsAndUsageViewers to read resource-availability in tenancy
Allow group LimitsAndUsageViewers to read resource-availability in compartment A
For limit definitions, services, and values APIs (only at the tenant level):
Allow group LimitsAndUsageViewers to inspect resource-availability in tenancy
For limit values APIs (doesn't include definitions or services), the following policy is also supported:
Allow group LimitsAndUsageViewers to inspect limits in tenancy
Viewing a Tenancy's Limits and Usage (By Region) 🔗
If you're in the Administrators group, you have permission to view the limits and usage. If you're not, here's an example IAM policy that grants the required permission to users in a group called LimitsAndUsageViewers:
Copy
Allow group LimitsAndUsageViewers to inspect resource-availability in tenancy
READ resource-availability is required to obtain the resource availability. Four APIs are available:
The Console might not display limits and usage information for all Oracle Cloud Infrastructure services or resources.
In the Console: Open the navigation menu and select Governance & Administration. Under Tenancy Management, select Limits, Quotas and Usage.
Your resource limits, quotas, and usage for the specific region are displayed, divided by service. You can use the filters to filter by Service, Scope, Resource, Subscription, and Compartment.
Note
The Subscription field is only selectable for certain combinations of service and scope. For example, when selecting the Database service and a particular Scope, a <subscription_ID>-<subscription_name> subscription can be selected, and the Limits, Quotas and Usage page reloads to display the limits specific to the associated subscription.
When You Reach a Service Limit 🔗
When you reach the service limit for a resource, you receive an error when you try to create a new resource of that type. You're then prompted to submit a request to increase the limit. You can't create a new resource until you're granted an increase to the service limit, or you delete an existing resource.
In addition, limit increase requests might not be approved because of security concerns or if limit increases aren't allowed for a particular resource.
Note
Service limits apply to a specific scope, and when the service limit in one scope is reached, you might still have resources available to you in other scopes (for example, other availability domains).
You can submit a request to increase your service limits from within the Console. If you try to create a resource for which a limit has been met, you're prompted to submit a limit increase request. Also, you can open the request from the service limits page, or by clicking the link under the Help menu ().
The following procedure applies to requests for service limit increases. For details about the subscribed region limit and how to request an increase to such limits, see Subscribed Region Limits.
Open the Help menu (). Under the Support section, click Request service limit increase.
On the Limit Increase tab, enter the following:
Service Category: Select the appropriate category for the request.
Resource: Select the appropriate resource (for example, Other Limits).
Depending on the resource you select, more fields might display for more specific information.
Subscription: Optionally, select the subscription associated with the request.
When updating your service limits for a subscription, an administrator in your tenancy must set up the following required policy which you can view by clicking View Policy Statement. The View Policy Statement panel opens with the following policy you can copy:
Copy
Allow group <group_name> to READ organizations-assigned-subscription in tenancy
Where <group_name> is the group or groups (separated by a comma) that need access in the Console.
Subscriptions aren't applicable to all resource types. If you select a subscription, the limit update applies only to resources provisioned in the associated subscription. When None is selected, the limit increase applies to the displayed region or availability domain.
Reason for request: Enter a reason for the request. If the request is urgent or unusual, then provide details here. Avoid entering confidential information.
Click Additional Request to add more request reasons.
Click Create Support Request.
After you submit the request, it's processed. A response can take anywhere from a few minutes to a few days. If the request is granted, then a confirmation email is sent to the address provided in the primary contact details.
If Oracle requires extra information about the request, then a follow-up email is sent to the address provided in the primary contact details.
Limits by Service 🔗
Click a service name to view the default limits. Note the scope that each limit applies to (for example, per availability domain, per region, per tenant, and so on).
Service limits in this topic define their limits in terms of the following pricing models (depending on the service, however, not all apply):
Many services have the same limits for Pay As You Go and Trial, and are listed as such in the following tables (Pay As You Go or Trial), while some services have different values for Pay As You Go compared with Trial, and so the Trial limit values are listed separately. Some services, meanwhile, can also have separate Always Free-eligibleresource limits.
Note
Some services have extra limits. For more information, see the overview of each service. To view the latest limit values for a service, also see the Console's Limits, Quotas and Usage page.
Dynamic Limits 🔗
Some of these limits can appear as Dynamic in the Console's Limits, Quotas and Usage page. Oracle Universal Credits and Pay As You Go or Trial customers have access to a dynamic amount of the particular resource, based on tenancy resource consumption and growth. Access to this resource increases over time.
For shapes that support container instances, service limits are shared between Compute resources and Container Instances resources.
Resource
Limit Name
Oracle Universal Credits
Pay As You Go or Trial
Total OCPUs (cores) for instances that are created using shapes in the VM.Standard2 and BM.Standard2 series
standard2-core-count
2,000
6
Total OCPUs (cores) for instances that are created using shapes in the VM.Standard3 and BM.Standard3 series
standard3-core-count
2,000 - commercial realm
6
Total memory for instances that are created using shapes in the VM.Standard3 and BM.Standard3 series
standard3-memory-count
32,000 GB - commercial realm
96 GB
Total OCPUs (cores) for instances that are created using shapes in the VM.Standard.E2.1.Micro series
standard-e2-micro-core-count
2
2
Total OCPUs (cores) for instances that are created using shapes in the VM.Standard.E2 and BM.Standard.E2 series
standard-e2-core-count
2,000
6
Total OCPUs (cores) for Compute instances that use shapes in the VM.Standard.E3 and BM.Standard.E3 series and container instances that use the CI.Standard.E3.Flex shape
Note: This service limit applies to both Compute and Container Instances resources. See Container Instances Limits.
standard-e3-core-ad-count
2,000 - commercial realm
6 - commercial realm
Total memory for Compute instances that use shapes in the VM.Standard.E3 and BM.Standard.E3 series and container instances that use the CI.Standard.E3.Flex shape
Note: This service limit applies to both Compute and Container Instances resources. See Container Instances Limits.
standard-e3-memory-count
32,000 GB - commercial realm
96 GB - commercial realm
Total OCPUs (cores) for Compute instances that use shapes in the VM.Standard.E4 and BM.Standard.E4 series and container instances that use the CI.Standard.E4.Flex shape
Note: This service limit applies to both Compute and Container Instances resources. See Container Instances Limits.
standard-e4-core-count
2,000 - commercial realm
6 - commercial realm
Total memory for Compute instances that use shapes in the VM.Standard.E4 and BM.Standard.E4 series and container instances that use the CI.Standard.E4.Flex shape
Note: This service limit applies to both Compute and Container Instances resources. See Container Instances Limits.
standard-e4-memory-count
32,000 GB - commercial realm
96 GB - commercial realm
Total OCPUs (cores) for Compute instances that use shapes in the VM.Standard.E5 and BM.Standard.E5 series and container instances that use the CI.Standard.E5.Flex shape
Note: This service limit applies to both Compute and Container Instances resources. See Container Instances Limits.
standard-e5-core-count
384 - commercial realm
6 - commercial realm
Total memory for Compute instances that use shapes in the VM.Standard.E5 and BM.Standard.E5 series and container instances that use the CI.Standard.E5.Flex shape
Note: This service limit applies to both Compute and Container Instances resources. See Container Instances Limits.
standard-e5-memory-count
4608 GB - commercial realm
72 GB
Total OCPUs (cores) for instances that are created using shapes in the VM.Standard.A1 and BM.Standard.A1 series
standard-a1-core-count
2,000 - commercial realm
16 - commercial realm
Total memory for instances that are created using shapes in the VM.Standard.A1 and BM.Standard.A1 series
standard-a1-memory-count
12,800 GB - commercial realm
96 GB - commercial realm
Total OCPUs (2 cores) for instances that are created using shapes in the VM.Standard.A2.Flex series
standard-a2-core-count
(Note: For standard-a2-core-count, use OCPU value for limit. For A2, 1 OCPU=2 cores.)
1,000 - commercial realm
8 - commercial realm
Total memory for instances that are created using shapes in the VM.Standard.A2.Flex series
standard-a2-memory-count
12,800 GB - commercial realm
96 GB - commercial realm
Total OCPUs (cores) for instances that are created using shapes in the VM.DenseIO2 and BM.DenseIO2 series
Total OCPUs (cores) for instances that are created using shapes in the VM.DenseIO.E4 and BM.DenseIO.E4 series
dense-io-e4-core-count
2,000 - commercial realm (Australia East (Sydney), Australia Southeast (Melbourne), Brazil East (Sao Paulo), Brazil Southeast (Vinhedo), Canada Southeast (Montreal), Canada Southeast (Toronto), Germany Central (Frankfurt), India South (Hyderabad), India West (Mumbai), Italy Northwest (Milan), Japan Central (Osaka), Japan East (Tokyo), Netherlands Northwest (Amsterdam), Saudi Arabia West (Jeddah), Singapore (Singapore), South Korea Central (Seoul), Sweden Central (Stockholm), UK South (London), US East (Ashburn), US West (Phoenix), US West (San Jose))
Total memory for instances that are created using shapes in the VM.DenseIO.E4 and BM.DenseIO.E4 series
dense-io-e4-memory-count
32,000 GB - commercial realm (Australia East (Sydney), Australia Southeast (Melbourne), Brazil East (Sao Paulo), Brazil Southeast (Vinhedo), Canada Southeast (Montreal), Canada Southeast (Toronto), Germany Central (Frankfurt), India South (Hyderabad), India West (Mumbai), Italy Northwest (Milan), Japan Central (Osaka), Japan East (Tokyo), Netherlands Northwest (Amsterdam), Saudi Arabia West (Jeddah), Singapore (Singapore), South Korea Central (Seoul), Sweden Central (Stockholm), UK South (London), US East (Ashburn), US West (Phoenix), US West (San Jose))
Total OCPUs (cores) for instances that are created using shapes in the VM.Optimized3 and BM.Optimized3 series
optimized3-core-count
1,500 - commercial realm (US East (Ashburn), US West (Phoenix))
500 - commercial realm (Australia East (Sydney), Australia Southeast (Melbourne), Brazil East (Sao Paulo), Brazil Southeast (Vinhedo), Canada Southeast (Montreal), Canada Southeast (Toronto), France Central (Paris), France South (Marseille), Germany Central (Frankfurt), India South (Hyderabad), India West (Mumbai), Israel Central (Jerusalem), Italy Northwest (Milan), Japan Central (Osaka), Japan East (Tokyo), Singapore (Singapore), South Africa Central (Johannesburg), South Korea Central (Seoul), South Korea North (Chuncheon), Sweden Central (Stockholm), Switzerland North (Zurich), UAE East (Dubai), UK South (London), US West (San Jose))
6 - commercial realm (Australia East (Sydney), Australia Southeast (Melbourne), Brazil East (Sao Paulo), Brazil Southeast (Vinhedo), Canada Southeast (Montreal), Canada Southeast (Toronto), France Central (Paris), France South (Marseille), Germany Central (Frankfurt), India South (Hyderabad), India West (Mumbai), Israel Central (Jerusalem), Italy Northwest (Milan), Japan Central (Osaka), Japan East (Tokyo), Singapore (Singapore), South Africa Central (Johannesburg), South Korea Central (Seoul), South Korea North (Chuncheon), Sweden Central (Stockholm), Switzerland North (Zurich), UAE East (Dubai), UK South (London), US East (Ashburn), US West (Phoenix), US West (San Jose))
Total memory for instances that are created using shapes in the VM.Optimized3 and BM.Optimized3 series
optimized3-memory-count
21,000 GB - commercial realm (US East (Ashburn), US West (Phoenix))
7,000 GB - commercial realm (Australia East (Sydney), Australia Southeast (Melbourne), Brazil East (Sao Paulo), Brazil Southeast (Vinhedo), Canada Southeast (Montreal), Canada Southeast (Toronto), France Central (Paris), France South (Marseille), Germany Central (Frankfurt), India South (Hyderabad), India West (Mumbai), Israel Central (Jerusalem), Italy Northwest (Milan), Japan Central (Osaka), Japan East (Tokyo), Singapore (Singapore), South Africa Central (Johannesburg), South Korea Central (Seoul), South Korea North (Chuncheon), Sweden Central (Stockholm), Switzerland North (Zurich), UAE East (Dubai), UK South (London), US West (San Jose))
84 GB - commercial realm (Australia East (Sydney), Australia Southeast (Melbourne), Brazil East (Sao Paulo), Brazil Southeast (Vinhedo), Canada Southeast (Montreal), Canada Southeast (Toronto), France Central (Paris), France South (Marseille), Germany Central (Frankfurt), India South (Hyderabad), India West (Mumbai), Israel Central (Jerusalem), Italy Northwest (Milan), Japan Central (Osaka), Japan East (Tokyo), Singapore (Singapore), South Africa Central (Johannesburg), South Korea Central (Seoul), South Korea North (Chuncheon), Sweden Central (Stockholm), Switzerland North (Zurich), UAE East (Dubai), UK South (London), US East (Ashburn), US West (Phoenix), US West (San Jose))
Total OCPUs (cores) for instances that are created using the DVH.Standard2.52 shape
dvh-standard2-core-count
52
52
Total OCPUs (cores) for instances that are created using the DVH.Standard.E2.64 shape
Limits apply to each availability domain. Capacity reservations aren't available with Free Tier accounts. For most pay-as-you-go customers, the service limit is implemented by default. If you're a pay-as-you-go customer and you're unable to make capacity reservations, Contact Us.
Capacity reservation limits have the following known issues:
When viewing limits, quotas, and usage in the Console, Reservable Cores and Reservable Memory indicate the service limit. Reserved Cores and Reserved Memory indicate current usage.
To request a limit increase for capacity reservations, in the Request Service Limit Updates form, for Resource, select Reservable Cores or Reservable Memory for the relevant shape.
Resource
Limit Name
Oracle Universal Credits
Pay As You Go or Trial
Reservable OCPUs (cores) for instances that are created using shapes in the VM.Standard2 and BM.Standard2 series
Reservable OCPUs (cores) for instances that are created using shapes in the VM.DenseIO.E4 and BM.DenseIO.E4 series
dense-io-e4-core-count-reservable
2,000 - commercial realm (Australia East (Sydney), Australia Southeast (Melbourne), Brazil East (Sao Paulo), Brazil Southeast (Vinhedo), Canada Southeast (Montreal), Canada Southeast (Toronto), Germany Central (Frankfurt), India South (Hyderabad), India West (Mumbai), Italy Northwest (Milan), Japan Central (Osaka), Japan East (Tokyo), Netherlands Northwest (Amsterdam), Saudi Arabia West (Jeddah), Singapore (Singapore), South Korea Central (Seoul), Sweden Central (Stockholm), UK South (London), US East (Ashburn), US West (Phoenix), US West (San Jose))
Reservable memory for instances that are created using shapes in the VM.DenseIO.E4 and BM.DenseIO.E4 series
dense-io-e4-memory-count-reservable
32,000 GB - commercial realm (Australia East (Sydney), Australia Southeast (Melbourne), Brazil East (Sao Paulo), Brazil Southeast (Vinhedo), Canada Southeast (Montreal), Canada Southeast (Toronto), Germany Central (Frankfurt), India South (Hyderabad), India West (Mumbai), Italy Northwest (Milan), Japan Central (Osaka), Japan East (Tokyo), Netherlands Northwest (Amsterdam), Saudi Arabia West (Jeddah), Singapore (Singapore), South Korea Central (Seoul), Sweden Central (Stockholm), UK South (London), US East (Ashburn), US West (Phoenix), US West (San Jose))
Reservable OCPUs (cores) for instances that are created using shapes in the VM.Optimized3 and BM.Optimized3 series
optimized3-core-count-reservable
1,500 - commercial realm (US East (Ashburn), US West (Phoenix))
500 - commercial realm (Australia East (Sydney), Australia Southeast (Melbourne), Brazil East (Sao Paulo), Brazil Southeast (Vinhedo), Canada Southeast (Montreal), Canada Southeast (Toronto), France Central (Paris), France South (Marseille), Germany Central (Frankfurt), India South (Hyderabad), India West (Mumbai), Israel Central (Jerusalem), Italy Northwest (Milan), Japan Central (Osaka), Japan East (Tokyo), Singapore (Singapore), South Africa Central (Johannesburg), South Korea Central (Seoul), South Korea North (Chuncheon), Sweden Central (Stockholm), Switzerland North (Zurich), UAE East (Dubai), UK South (London), US West (San Jose))
Reservable memory for instances that are created using shapes in the VM.Optimized3 and BM.Optimized3 series
optimized3-memory-count-reservable
21,000 GB commercial realm (US East (Ashburn), US West (Phoenix))
7,000 GB commercial realm (Australia East (Sydney), Australia Southeast (Melbourne), Brazil East (Sao Paulo), Brazil Southeast (Vinhedo), Canada Southeast (Montreal), Canada Southeast (Toronto), France Central (Paris), France South (Marseille), Germany Central (Frankfurt), India South (Hyderabad), India West (Mumbai), Israel Central (Jerusalem), Italy Northwest (Milan), Japan Central (Osaka), Japan East (Tokyo), Singapore (Singapore), South Africa Central (Johannesburg), South Korea Central (Seoul), South Korea North (Chuncheon), Sweden Central (Stockholm), Switzerland North (Zurich), UAE East (Dubai), UK South (London), US West (San Jose))
Service limits are shared between Compute resources and Container Instances resources. In the Console, limits for Container Instances resources display under the filter drop-down list for the Compute service.
Resource
Oracle Universal Credits
Pay As You Go or Trial
Total OCPUs (cores) for Compute instances that use shapes in the VM.Standard.E3 and BM.Standard.E3 series and container instances that use the CI.Standard.E3.Flex shape
Note: This service limit applies to both Compute and Container Instances resources. See Compute Instances.
2,000 - commercial realm
6 - commercial realm
Total memory for Compute instances that use shapes in the VM.Standard.E3 and BM.Standard.E3 series and container instances that use the CI.Standard.E3.Flex shape
Note: This service limit applies to both Compute and Container Instances resources. See Compute Instances.
32,000 GB - commercial realm
96 GB - commercial realm
Total OCPUs (cores) for Compute instances that use shapes in the VM.Standard.E4 and BM.Standard.E4 series and container instances that use the CI.Standard.E4.Flex shape
Note: This service limit applies to both Compute and Container Instances resources. See Compute Instances.
2,000 - commercial realm
6 - commercial realm
Total memory for Compute instances that use shapes in the VM.Standard.E4 and BM.Standard.E4 series and container instances that use the CI.Standard.E4.Flex shape
Note: This service limit applies to both Compute and Container Instances resources. See Compute Instances.
To place an order for the Oracle-provided Data Transfer Appliance used for appliance-based data transfer and data export jobs, request the required entitlement for your tenancy through the Console or CLI. See Requesting Appliance Entitlement for instructions.
The buyer of your tenancy will be required to e-sign a Terms and Conditions document. After Oracle receives the signed document you will have the entitlement to request and use the Data Transfer Appliance. Appliance-Based Data Import and Data Export each come with a service limit of 2. File a service request if you need to increase that number.
50 cores (Germany Central (Frankfurt), UK South (London))
2 cores
Note
Autonomous Exadata Infrastructure: Exadata X8 (Exadata.Quarter3.100,
Exadata.Half3.200, and Exadata.Full3.300) and Exadata X7 limits
(Exadata.Quarter2.92, Exadata.Half2.184, and Exadata.Full2.368) include the
corresponding Autonomous Exadata Infrastructure shapes.
Total VM DB Block Storage: Includes block storage for all
VM.Standard1 and VM.Standard2 virtual machine databases.
BM.DenseIO1.36: This DB system shape is available only to monthly universal credit customers with tenancies existing on or before November 9th, 2018, in the US West (Phoenix), US East (Ashburn), and Germany Central (Frankfurt) regions.
Always Free
Autonomous Database: Each of the two Always Free
Autonomous Databases available in your tenancy can be provisioned with your choice of Autonomous Database for Transaction Processing and Mixed Workloads or Autonomous Database for Analytics and Data Warehousing workload types.
Default limits apply to each tenant or availability domain, as specified below. Approved limit increases apply to a specific region.All resources in the table below are eligible for an increase.
Note
Limits can't be increased without SPF and DKIM set up for each sending domain.
Resource
Limit Name
Oracle Universal Credits
Pay As You Go
Trial
Always Free*
Emails sent in last 24 hours
max-emails-day
50,000
50000
200
0
Maximum approved senders
approved-sender-count
10,000
10,000
2000
10
SMTP credentials per user
2
2
2
Emails sent per minute
sendrate
18,000
18,000
10
10
Message size (after base64 encoding and headers)
max-message-size
2 MB
2 MB
2 MB
2 MB
Note
Always free resources are for a tenancy and can't be increased.
Note
An email is defined as either a single recipient (as defined in the To:, CC:, or BCC: fields) or a 2 MB chunk of an email.
Email examples:
A single request with 10 recipients (TO:, CC:, or BCC:) equals 10 emails.
A 10 MB email sent to a single recipient is equal to 10 MB divided by 2 MB per email. This equals 5 emails.
A single email request with a message size of 10 MB and 10 recipients is equal to 10 MB divided by 2 MB per email multiplied by 10 recipients. This equals 50 emails.
The email volume limit applies to unique recipients among all emails sent. For example, a single email sent to 100 recipients would count the same as 100 individual emails each sent to a single recipient.
Note
Email Delivery supports messages up to 2 MB, inclusive of message headers, body, and attachments. If you have SPF and DKIM set up on your sending domain, you can request this limit to be increased based on your requirement. The maximum size that can be requested is 60 MB.
This is for new tenancies in regions that have been updated to use identity domains. To check that you're using the correct documentation for your IAM service, see Cloud Identity Documentation.
IAM limits are global.
The subscription type controls the number of identity domains of each type.
See IAM Object Limits for object limits for each identity domain type.
This is for tenancies in regions that haven't been updated to use identity domains. To check that you're using the correct documentation for your IAM service, see Cloud Identity Documentation.
Limits are set per tenancy and are applied at the regional level. For example, if you subscribe to two regions, IAD and FRA, you get 10 virtual vaults in IAD and another 10 virtual vaults in FRA.
Virtual Vault Limits
Resource
Oracle Universal Credits or Pay As You Go
Always Free or Trial
Vaults
Note: Replicated vaults count against the service limits of the region they are created in.
10
Contact Us to request an increase. Limit is set at the regional level.
Key versions can exist across a varying combination of master encryption keys in a vault.
Key versions, whether enabled or disabled, count against your limits.
When calculating usage against service limits for asymmetric keys, each key version increments the count by two. This accounts for both the public key and the private key.
Replicated key versions count against the limits of the region they are stored in.
Key versions can exist across a varying combination of master encryption keys in a vault.
Key versions, whether enabled or disabled, count against your limits.
When calculating usage against service limits for asymmetric keys, each key version increments the count by two. This accounts for both the public key and the private key.
Replicated key versions count against the service limits of the region they are stored in.
3000 (hardware protected)
Note that 3000 keys is the maximum number that can be stored in a private vault. To store more than 3000 keys, create another private vault.
Keys, whether enabled or disabled, count against your limits.
When calculating usage against service limits for asymmetric keys, each key version increments the count by two. This accounts for both the public key and the private key.
3000
Note that 3000 keys is the maximum number that can be stored in an HSM cluster. To store more than 3000 keys, create another HSM Cluster.
Note: Secrets, regardless of rotation state, count against your limits. All secrets can be in one vault or spread across the allowable number of vaults.
15 enhanced clusters per OCI regionTo request more, contact us.
1 enhanced cluster per OCI regionTo request more, contact us.
Managed Nodes per Cluster
node-count
Basic cluster: 1000 managed nodes per basic cluster
Enhanced cluster: 2000 managed (or self-managed) nodes per enhanced cluster
Basic cluster: 1000 managed nodes per basic cluster
Enhanced cluster: 2000 managed (or self-managed) nodes per enhanced cluster
Managed Nodes per Node Pool
-
1000 nodes per node pool
1000 nodes per node pool
Pods per Managed Node
-
110 pods per managed node
110 pods per managed node
Virtual Nodes per Region (enhanced clusters only)
virtual-node-count
9 virtual nodes per OCI region
3 virtual nodes per OCI region
Pods per Virtual Node (enhanced clusters only)
-
500 pods per virtual node
2 pods per virtual node
Note
You can contact us to request an increase to the number of enhanced clusters per region. However, the number of basic clusters per region cannot be increased.
Some resources can have fractional usage and availability, and the Service Limits API
reflects this accordingly. If the resource is a fractional one, usage reflects the
rounded up value of the fractional usage, and for availability, the
rounded down value of the fractional availability. As a result, these
fractional availability and usage attributes help indicate the most accurate usage
and availability.
For example, if a resource has 2.4 used, 4.6 available, the following API response is
returned: