AWS opensearch-service documentation change
Summary
Added details about redundancy settings affecting OCU allocation in OpenSearch Serverless
Security assessment
Focuses on availability and scaling mechanics rather than security controls or vulnerabilities.
Diff
diff --git a/opensearch-service/latest/developerguide/serverless-scaling.md b/opensearch-service/latest/developerguide/serverless-scaling.md index eba8ffda4..da6d6f59a 100644 --- a//opensearch-service/latest/developerguide/serverless-scaling.md +++ b//opensearch-service/latest/developerguide/serverless-scaling.md @@ -11 +11 @@ With Amazon OpenSearch Serverless, you don't have to manage capacity yourself. O -When you create your first collection, OpenSearch Serverless instantiates a total of four OCUs (two for indexing and two for search). These OCUs always exist, even when there's no indexing or search activity. All subsequent collections can share these OCUs (except for collections with unique AWS KMS keys, which instantiate their own set of four OCUs). If needed, OpenSearch Serverless automatically scales out and adds additional OCUs as your indexing and search usage grows. When traffic on your collection endpoint decreases, capacity scales back down to the minimum number of OCUs required for your data size. For the search and time series collection, the number of OCUs required when idle is proportional to the data size and index count. For vectors, it depends on both the memory (RAM) to store vector graphs and disk space to store indices. If not in an idle state, OCU requirements take both of these into account. +When you create your first collection, OpenSearch Serverless instantiates OCUs based on your redundancy settings. By default, redundant active replicas are enabled, which means that a total of four OCUs are instantiated (two for indexing and two for search) to ensure high availability with standby nodes in another Availability Zone. For development and testing purposes, you can disable the **Enable redundancy** setting for a collection, which eliminates the standby replicas and only instantiates two OCUs (one for indexing and one for search). These OCUs always exist, even when there's no indexing or search activity. All subsequent collections can share these OCUs (except for collections with unique AWS KMS keys, which instantiate their own set of OCUs). If needed, OpenSearch Serverless automatically scales out and adds additional OCUs as your indexing and search usage grows. When traffic on your collection endpoint decreases, capacity scales back down to the minimum number of OCUs required for your data size. For the search and time series collection, the number of OCUs required when idle is proportional to the data size and index count. For vectors, it depends on both the memory (RAM) to store vector graphs and disk space to store indices. If not in an idle state, OCU requirements take both of these into account.