AWS opensearch-service documentation change
Summary
Removed detailed pricing section and updated OpenSearch compatibility from 2.x to 3.x. Added collection type limitations and revised compute capacity explanations.
Security assessment
The changes are administrative updates (version compatibility, pricing structure, collection type notes) without any mention of vulnerabilities, security patches, or security incidents. No security features were added or modified.
Diff
diff --git a/opensearch-service/latest/developerguide/serverless-overview.md b/opensearch-service/latest/developerguide/serverless-overview.md index 098ef84a8..493e22b1d 100644 --- a//opensearch-service/latest/developerguide/serverless-overview.md +++ b//opensearch-service/latest/developerguide/serverless-overview.md @@ -7 +7 @@ -Use cases for OpenSearch ServerlessHow it worksChoosing a collection typePricingSupported AWS RegionsLimitations +Use cases for OpenSearch ServerlessHow it worksChoosing a collection typeSupported AWS RegionsLimitations @@ -17 +17 @@ Collections use the same high-capacity, distributed, and highly available storag -Currently, serverless collections run OpenSearch version 2.17.x. As new versions are released, OpenSearch Serverless automatically upgrades collections to incorporate new features, bug fixes, and performance improvements. +OpenSearch Serverless is compatible with open source OpenSearch. As new versions are released, OpenSearch Serverless automatically upgrades collections to incorporate new features, bug fixes, and performance improvements. @@ -19 +19 @@ Currently, serverless collections run OpenSearch version 2.17.x. As new versions -OpenSearch Serverless supports the same ingest and query API operations as the OpenSearch open source suite, so you can continue to use your existing clients and applications. Your clients must be compatible with OpenSearch 2.x in order to work with OpenSearch Serverless. For more information, see [Ingesting data into Amazon OpenSearch Serverless collections](./serverless-clients.html). +OpenSearch Serverless supports the same ingest and query API operations as the OpenSearch open source suite, so you can continue to use your existing clients and applications. Your clients must be compatible with OpenSearch 3.x in order to work with OpenSearch Serverless. For more information, see [Ingesting data into Amazon OpenSearch Serverless collections](./serverless-clients.html). @@ -29,2 +28,0 @@ OpenSearch Serverless supports the same ingest and query API operations as the O - * Pricing - @@ -65,3 +63 @@ The following image illustrates this decoupled architecture: -OpenSearch Serverless compute capacity for data ingestion, searching, and querying are measured in OpenSearch Compute Units (OCUs). Each OCU is a combination of 6 GiB of memory and corresponding virtual CPU (vCPU), as well as data transfer to Amazon S3. Each OCU includes enough hot ephemeral storage for 120 GiB of index data. - -When you create your first collection, OpenSearch Serverless instantiates two OCUs—one for indexing and one for search. To ensure high availability, it also launches a standby set of nodes in another Availability Zone. For development and testing purposes, you can disable the **Enable redundancy** setting for a collection, which eliminates the two standby replicas and only instantiates two OCUs. By default, the redundant active replicas are enabled, which means that a total of four OCUs are instantiated for the first collection in an account. +OpenSearch Serverless compute capacity for data ingestion, searching, and querying are measured in OpenSearch Compute Units (OCUs). Each OCU is a combination of 6 GiB of memory and corresponding virtual CPU (vCPU), as well as data transfer to Amazon S3. @@ -69 +65 @@ When you create your first collection, OpenSearch Serverless instantiates two OC -These OCUs exist even when there's no activity on any collection endpoints. All subsequent collections share these OCUs. When you create additional collections in the same account, OpenSearch Serverless only adds additional OCUs for search and ingest as needed to support the collections, according to the [capacity limits](./serverless-scaling.html#serverless-scaling-configure) that you specify. Capacity scales back down as your compute usage decreases. +OpenSearch Serverless provisions OCUs separately for search and indexing. OpenSearch Serverless only adds additional OCUs for search and ingest as needed to support the collections, according to the [capacity limits](./serverless-scaling.html#serverless-scaling-configure) that you specify. Capacity scales back down as your compute usage decreases. @@ -71 +67 @@ These OCUs exist even when there's no activity on any collection endpoints. All -For information about how you're billed for these OCUs, see Pricing. +For information about how you're billed for these OCUs, see [Amazon OpenSearch Service pricing](https://aws.amazon.com/opensearch-service/pricing/). @@ -78,0 +75,4 @@ OpenSearch Serverless supports three primary collection types: +###### Note + +Time series collections are only available for Classic collections. NextGen collections currently support Search and Vector search types only. + @@ -93 +93 @@ The collection types have the following notable **differences** : - * For _time series_ and _vector search_ collections, you can't index by custom document ID or update by upsert requests. This operation is reserved for search use cases. You can update by document ID instead. For more information, see [Supported OpenSearch API operations and permissions](./serverless-genref.html#serverless-operations). + * For _time series_ collections, you can't index by custom document ID or update by upsert requests. This operation is reserved for search use cases. You can update by document ID instead. For more information, see [Supported OpenSearch API operations and permissions](./serverless-genref.html#serverless-operations). @@ -100,36 +99,0 @@ The collection types have the following notable **differences** : -## Pricing - -AWS charges you for the following OpenSearch Serverless components: - - * Data ingestion compute - - * Search and query compute - - * Storage retained in Amazon S3 - - - - -One OCU comprises 6 GB of RAM, corresponding vCPU, GP3 storage, and data transfer to Amazon S3. The smallest unit you can be billed for is 0.5 OCU. AWS bills OCU on an hourly basis, with second-level granularity. In your account statement, you see an entry for compute in OCU-hours with a label for data ingestion and a label for search. AWS also bills you on a monthly basis for data stored in Amazon S3. It doesn't charge you for using OpenSearch Dashboards. - -When you create a collection with redundant active replicas, you're billed for a minimum of 1 OCU (0.5 OCU × 2) for ingestion, including both primary and standby, and 1 OCU (0.5 OCU × 2) for search: - - * 1 OCU (0.5 OCU × 2) for ingestion, including both primary and standby - - * 1 OCU (0.5 OCU × 2) for search - - - - -If you disable redundant active replicas, you're billed for a minimum of 1 OCU (0.5 OCU x 2) for the first collection in your account. All subsequent collections can share those OCUs. - -OpenSearch Serverless adds additional OCUs in increments of 1 OCU based on the compute power and storage needed to support your collections. You can configure a maximum number of OCUs for your account in order to control costs. - -###### Note - -Collections with unique AWS KMS keys can't share OCUs with other collections unless they are part of the same collection group. For more information, see [Collection groups](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless-collection-groups.html). - -OpenSearch Serverless attempts to use the minimum required resources to account for changing workloads. The number of OCUs provisioned at any time can vary and isn't exact. Over time, the algorithm that OpenSearch Serverless uses will continue to improve in order to better minimize system usage. - -For full pricing details, see [Amazon OpenSearch Service pricing](https://aws.amazon.com/opensearch-service/pricing/). - @@ -160 +124 @@ OpenSearch Serverless has the following limitations: - * The refresh interval for indexes in vector search collections is approximately 60 seconds. The refresh interval for indexes in search and time series collections is approximately 10 seconds. + * The refresh interval for indexes in search and time series collections is approximately 10 seconds. @@ -164,2 +127,0 @@ OpenSearch Serverless has the following limitations: - * Geospatial features available on OpenSearch versions up to 2.1 are supported. -