AWS opensearch-service documentation change
Summary
Updated terminology from 'OR1 instances' to 'OpenSearch optimized instances' throughout the document, added OR2/OM2 instance types, and adjusted section headers/links for consistency
Security assessment
Changes focus on branding consistency and expanded instance type support rather than addressing security vulnerabilities. While automatic data recovery is mentioned, this is presented as a reliability feature rather than a security fix. No security vulnerabilities, access controls, or encryption-related changes are present.
Diff
diff --git a/opensearch-service/latest/developerguide/or1.md b/opensearch-service/latest/developerguide/or1.md index 5715cf289..bcb0b1272 100644 --- a//opensearch-service/latest/developerguide/or1.md +++ b//opensearch-service/latest/developerguide/or1.md @@ -5 +5 @@ -LimitationsTuning for better ingestion throughputHow OpenSearch optimized instances differ from other instancesHow OR1 differs from UltraWarm storageProvisioning a domain with OR1 instances +LimitationsTuning for better ingestion throughputHow OpenSearch optimized instances differ from other instancesHow OpenSearch optimized instances differ from UltraWarm storageProvisioning a domain with OpenSearch optimized instances @@ -9 +9 @@ LimitationsTuning for better ingestion throughputHow OpenSearch optimized instan -The OpenSearch optimized instance family for Amazon OpenSearch Service is a cost-effective solution for storing large volumes of data. A domain with OR1 instances uses Amazon Elastic Block Store (Amazon EBS) `gp3` or `io1` volumes for primary storage, with data copied synchronously to Amazon S3 as it arrives. This storage structure provides increased indexing throughput with high durability. The OpenSearch optimized instance family also supports automatic data recovery in the event of failure. For information about OR1 instance type options, see [Current generation instance types](./supported-instance-types.html#latest-gen). +The OpenSearch optimized instance family for Amazon OpenSearch Service is a cost-effective solution for storing large volumes of data. A domain with OpenSearch optimized instances (OR1, OR2, OM2) uses Amazon Elastic Block Store (Amazon EBS) `gp3` or `io1` volumes for primary storage, with data copied synchronously to Amazon S3 as it arrives. This storage structure provides increased indexing throughput with high durability. The OpenSearch optimized instance family also supports automatic data recovery in the event of failure. For information about OpenSearch optimized instance type options, see [Current generation instance types](./supported-instance-types.html#latest-gen). @@ -11 +11 @@ The OpenSearch optimized instance family for Amazon OpenSearch Service is a cost -If you're running indexing heavy operational analytics workloads such as log analytics, observability, or security analytics, you can benefit from the improved performance and compute efficiency of OR1 instances. In addition, the automatic data recovery offered by OR1 instances improves the overall reliability of your domain. +If you're running indexing heavy operational analytics workloads such as log analytics, observability, or security analytics, you can benefit from the improved performance and compute efficiency of OpenSearch optimized instances. In addition, the automatic data recovery offered by OpenSearch optimized instances improves the overall reliability of your domain. @@ -13 +13 @@ If you're running indexing heavy operational analytics workloads such as log ana -OpenSearch Service sends storage-related OR1 metrics to Amazon CloudWatch. For a list of available metrics, see [OR1 metrics](./managedomains-cloudwatchmetrics.html#managedomains-cloudwatchmetrics-or1). +OpenSearch Service sends storage-related OpenSearch optimized instance metrics to Amazon CloudWatch. For a list of available metrics, see [OR1 metrics](./managedomains-cloudwatchmetrics.html#managedomains-cloudwatchmetrics-or1). @@ -15 +15 @@ OpenSearch Service sends storage-related OR1 metrics to Amazon CloudWatch. For a -OR1 instances are available on-demand or with Reserved Instance pricing, with an hourly rate for the instances and storage provisioned in Amazon EBS and Amazon S3. +OpenSearch optimized instances are available on-demand or with Reserved Instance pricing, with an hourly rate for the instances and storage provisioned in Amazon EBS and Amazon S3. @@ -25 +25 @@ OR1 instances are available on-demand or with Reserved Instance pricing, with an - * How OR1 differs from UltraWarm storage + * How OpenSearch optimized instances differ from UltraWarm storage @@ -27 +27 @@ OR1 instances are available on-demand or with Reserved Instance pricing, with an - * Provisioning a domain with OR1 instances + * Provisioning a domain with OpenSearch optimized instances @@ -34 +34 @@ OR1 instances are available on-demand or with Reserved Instance pricing, with an -Consider the following limitations when using OR1 instances for your domain. +Consider the following limitations when using OpenSearch optimized instances for your domain. @@ -44 +44 @@ Consider the following limitations when using OR1 instances for your domain. - * The refresh interval for indexes on OR1 instances must be 10 seconds or higher. The default refresh interval for OR1 instances is 10 seconds. + * The refresh interval for indexes on OpenSearch optimized instances must be 10 seconds or higher. The default refresh interval for OpenSearch optimized instances is 10 seconds. @@ -51 +51 @@ Consider the following limitations when using OR1 instances for your domain. -To get the best indexing throughput from your OR1 instances, we recommend that you do the following: +To get the best indexing throughput from your OpenSearch optimized instances, we recommend that you do the following: @@ -81 +81 @@ The `IndexingLatency` metric is not affected, as it doesn’t include time to sy -## How OR1 differs from UltraWarm storage +## How OpenSearch optimized instances differ from UltraWarm storage @@ -83 +83 @@ The `IndexingLatency` metric is not affected, as it doesn’t include time to sy -OpenSearch Service provides UltraWarm instances that are a cost-effective way to store large amounts of read-only data. Both OR1 and UltraWarm instances store data locally in Amazon EBS and remotely in Amazon S3. However, OR1 and UltraWarm instances differ in several important ways: +OpenSearch Service provides UltraWarm instances that are a cost-effective way to store large amounts of read-only data. Both OpenSearch optimized and UltraWarm instances store data locally in Amazon EBS and remotely in Amazon S3. However, OpenSearch optimized and UltraWarm instances differ in several important ways: @@ -85 +85 @@ OpenSearch Service provides UltraWarm instances that are a cost-effective way to - * OR1 instances keep a copy of data in _both_ your local and remote store. In UltraWarm instances, data is kept primarily in remote store to reduce storage costs. Depending on your usage patterns, data can be moved to local storage. + * OpenSearch optimized instances keep a copy of data in _both_ your local and remote store. In UltraWarm instances, data is kept primarily in remote store to reduce storage costs. Depending on your usage patterns, data can be moved to local storage. @@ -87 +87 @@ OpenSearch Service provides UltraWarm instances that are a cost-effective way to - * OR1 instances are active and can accept read and write operations, whereas the data on UltraWarm instances is read-only until you manually move it back to hot storage. + * OpenSearch optimized instances are active and can accept read and write operations, whereas the data on UltraWarm instances is read-only until you manually move it back to hot storage. @@ -89 +89 @@ OpenSearch Service provides UltraWarm instances that are a cost-effective way to - * UltraWarm relies on index snapshots for data durability. OR1 instances, by comparison, perform replication and recovery behind the scenes. In the event of a red index, OR1 instances will automatically restore missing shards from your remote storage in Amazon S3. The recovery time varies depending on the volume of data to be recovered. + * UltraWarm relies on index snapshots for data durability. OpenSearch optimized instances, by comparison, perform replication and recovery behind the scenes. In the event of a red index, OpenSearch optimized instances will automatically restore missing shards from your remote storage in Amazon S3. The recovery time varies depending on the volume of data to be recovered. @@ -96 +96 @@ For more information about UltraWarm storage, see [UltraWarm storage for Amazon -## Provisioning a domain with OR1 instances +## Provisioning a domain with OpenSearch optimized instances @@ -98 +98 @@ For more information about UltraWarm storage, see [UltraWarm storage for Amazon -You can select OR1 instances for your data nodes when you create a new domain with the AWS Management Console or the AWS Command Line Interface (AWS CLI). You can then index and query the data using your existing tools. +You can select OpenSearch optimized instances for your data nodes when you create a new domain with the AWS Management Console or the AWS Command Line Interface (AWS CLI). You can then index and query the data using your existing tools. @@ -117 +117 @@ You can select OR1 instances for your data nodes when you create a new domain wi -To provision a domain that uses OR1 storage using the AWS CLI, you must provide the value of the specific OR1 instance type size in the `InstanceType`. +To provision a domain that uses OpenSearch optimized storage using the AWS CLI, you must provide the value of the specific instance type size (such as OR1, OR2, or OM2) in the `InstanceType`.