OpenSearch Serverless Collection Group Limit Jumps From 1,500 to 10,000!
Hey there, it's me, Shiichan! Today I found a quiet but genuinely useful limit increase for Amazon OpenSearch Serverless. The number of collections you can pack into a collection group just got a lot bigger, so let me walk you through it!
AWS What's NewWhat was announced?
From AWS What's New: the next generation of Amazon OpenSearch Serverless now supports up to 10,000 collections within a single collection group, up from the previous limit of 1,500.
Collection groups let multiple collections share OpenSearch Compute Units (OCUs). The neat part is that this works even when the collections are encrypted with different AWS KMS keys, while each collection still keeps its own security and access controls.
The story so far
Until now, a single collection group could hold at most 1,500 collections. For multi-tenant applications that provision one collection per tenant, that limit effectively capped how many tenants could share a single compute pool.
Once a workload approached 1,500 tenants, the only option was to create and operate another collection group. That's still more efficient than provisioning a separate set of OCUs per KMS key, but managing an ever-growing number of collection groups added real operational overhead.
What changes
With the limit raised to 10,000, a single collection group can now hold about 6.7 times as many collections as before. For teams running multi-tenant SaaS on OpenSearch Serverless, that means:
- You can fit far more tenants into the same shared compute pool without creating extra collection groups
- You can push OCU utilization higher, which lowers the cost per collection
- You end up managing fewer collection groups overall, which cuts operational overhead
And this higher limit applies automatically to both new and existing nextgen collection groups, so there's nothing you need to configure.
Dive Deep
This change applies in every AWS Region where the next generation of Amazon OpenSearch Serverless is available. The underlying mechanism, sharing OCUs across collections encrypted with different KMS keys, stays exactly the same; it's the container itself, the collection group, that got bigger.
For details on creating collection groups and the full set of limits, see the OpenSearch Serverless technical documentation and the service quotas page.
Wrap-up
- Amazon OpenSearch Serverless (nextgen) collection groups now support up to 10,000 collections, up from 1,500
- Collection groups let collections encrypted with different KMS keys share OCUs while keeping per-collection security intact
- Multi-tenant setups that provision one collection per tenant benefit the most
- The higher limit applies automatically to new and existing groups, no configuration needed
- A welcome update for anyone running, or planning, a large multi-tenant workload on a shared compute pool