AWS opensearch-service documentation change
Summary
Expanded documentation on OCU limits between account-level and collection groups, added capacity planning examples
Security assessment
The changes clarify resource allocation limits but do not introduce or modify security controls. No security vulnerabilities are addressed.
Diff
diff --git a/opensearch-service/latest/developerguide/collection-groups-capacity-limits.md b/opensearch-service/latest/developerguide/collection-groups-capacity-limits.md index 5c7aafeaa..df84c25dc 100644 --- a//opensearch-service/latest/developerguide/collection-groups-capacity-limits.md +++ b//opensearch-service/latest/developerguide/collection-groups-capacity-limits.md @@ -5 +5 @@ -Understanding collection group capacity limitsValid capacity limit valuesConfiguring capacity limitsMonitoring collection group capacityHow capacity limits are enforced +Understanding collection group capacity limitsValid capacity limit valuesUnderstanding the relationship between account-level and collection group OCU limitsConfiguring capacity limitsMonitoring collection group capacityHow capacity limits are enforced @@ -11 +11 @@ Collection groups provide granular control over resource allocation through mini -By default, there is a service quota (limit) for the number of collections in a collection group, the number of indexes in a collection, and the number of OCUs in a collection group. For more information, see [OpenSearch Serverless quotas](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/limits.html). +By default, there is a service quota (limit) for the number of collections in a collection group, the number of indexes in a collection, and the number of OCUs in a collection group. For more information, see [OpenSearch Serverless quotas](https://docs.aws.amazon.com/general/latest/gr/opensearch-service.html#opensearch-limits-serverless). @@ -32 +32 @@ Collection group capacity limits are decoupled from account-level limits. Accoun -When setting minimum and maximum OCU limits for a collection group, you can only use values from the following set: 1, 2, 4, 8, 16, and multiples of 16 (such as 32, 48, 64, 80, 96). +When setting minimum and maximum OCU limits for a collection group, you can only use values from the following set: 1, 2, 4, 8, 16, and multiples of 16 (such as 32, 48, 64, 80, 96) up to a maximum of 1,696 OCUs. @@ -36 +36,26 @@ Both minimum and maximum OCU limits are optional when you create a collection gr -The minimum OCU limit must be less than or equal to the maximum OCU limit. The sum of all maximum OCU limits across your account-level settings and all collection groups cannot exceed 1,700 OCUs per account. +The minimum OCU limit must be less than or equal to the maximum OCU limit. + +## Understanding the relationship between account-level and collection group OCU limits + +When planning your OpenSearch Serverless capacity, it's important to understand how account-level OCU limits and collection group OCU limits interact. The sum of the maximum OCU settings across all collection groups plus the maximum OCU setting at the account level must be less than or equal to the service quota limit per account. For current limit values, see [OpenSearch Serverless quotas](https://docs.aws.amazon.com/general/latest/gr/opensearch-service.html#opensearch-limits-serverless). + +###### Note + +Account-level maximum OCU settings apply only to collections not associated with any collection group. Collections within collection groups are governed by their respective collection group limits, not the account-level limits. + +This constraint applies to both indexing and search OCUs independently. For example, if you configure account-level settings and collection groups, you must ensure the total doesn't exceed the service quota limit for indexing OCUs and separately doesn't exceed the service quota limit for search OCUs. Additionally, you can create a maximum of 300 collection groups per account. + +###### Example: Planning capacity with account-level and collection group limits + +If you set the account-level maximum search OCU to 500 and the service quota limit is 1,700: + + * And create 2 collection groups, the sum of the maximum OCU for the 2 collection groups must be no more than 1,200 (1,700 - 500) + + * You could leave each collection group at the default maximum OCU of 96 (96 + 96 + 500 = 692), leaving headroom for future growth + + * Or you could increase each collection group's maximum to 600 (600 + 600 + 500 = 1,700), using the full capacity allowed by the service quota + + + + +This relationship is critical for capacity planning. Before creating new collection groups or increasing maximum OCU limits, verify that your total allocation doesn't exceed the service quota limit. If you reach this limit, you must either reduce the maximum OCU settings on existing collection groups or decrease your account-level maximum OCU settings to make room for new allocations.