AWS opensearch-service documentation change
Summary
Updated documentation to focus on migration workflows rather than general connectivity. Changes include rebranding section headers, updating links to relative paths, modifying example configurations (removing sts_role_arn placeholders, changing bucket names), and adjusting VPC network configuration instructions.
Security assessment
The changes primarily improve clarity and internal linking rather than addressing security vulnerabilities. While sts_role_arn references were removed from examples, there's no evidence this relates to a security fix. The VPC CIDR instruction change limits selection to default options but doesn't explicitly introduce new security controls.
Diff
diff --git a/opensearch-service/latest/developerguide/configure-client-self-managed-opensearch.md b/opensearch-service/latest/developerguide/configure-client-self-managed-opensearch.md index c2961447c..d30cc6838 100644 --- a//opensearch-service/latest/developerguide/configure-client-self-managed-opensearch.md +++ b//opensearch-service/latest/developerguide/configure-client-self-managed-opensearch.md @@ -5 +5 @@ -Connectivity to public OpenSearch clusters Connectivity to OpenSearch clusters in a VPC +Migrating from public OpenSearch clusters Migrating data from OpenSearch clusters in a VPC @@ -7 +7 @@ Connectivity to public OpenSearch clusters Connectivity to OpenSearch clusters i -# Using an OpenSearch Ingestion pipeline with OpenSearch +# Migrating data from self-managed OpenSearch clusters using Amazon OpenSearch Ingestion @@ -9 +9 @@ Connectivity to public OpenSearch clusters Connectivity to OpenSearch clusters i -You can use an OpenSearch Ingestion pipeline with self-managed OpenSearch or Elasticsearch to migrate data to Amazon OpenSearch Service domains and OpenSearch Serverless collections. OpenSearch Ingestion supports both public and private network configurations for the migration of data from self-managed OpenSearch and Elasticsearch. +You can use an Amazon OpenSearch Ingestion pipeline with self-managed OpenSearch or Elasticsearch to migrate data to Amazon OpenSearch Service domains and OpenSearch Serverless collections. OpenSearch Ingestion supports both public and private network configurations for the migration of data from self-managed OpenSearch and Elasticsearch. @@ -11 +11 @@ You can use an OpenSearch Ingestion pipeline with self-managed OpenSearch or Ela -## Connectivity to public OpenSearch clusters +## Migrating from public OpenSearch clusters @@ -19 +19 @@ Before you create your OpenSearch Ingestion pipeline, perform the following step - 1. Create a self-managed OpenSearch or Elastisearch cluster that contains the data you want to migrate and configure a public DNS name. + 1. Create a self-managed OpenSearch or Elastisearch cluster that contains the data you want to migrate and configure a public DNS name. For instructions, see [Create a cluster](https://opensearch.org/docs/latest/tuning-your-cluster/) in the OpenSearch documentation. @@ -21 +21 @@ Before you create your OpenSearch Ingestion pipeline, perform the following step - 2. Create an OpenSearch Service domain or OpenSearch Serverless collection where you want to migrate data to. For more information, see [Creating OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/createupdatedomains.html#createdomains) and [Creating collections](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless-manage.html#serverless-create). + 2. Create an OpenSearch Service domain or OpenSearch Serverless collection where you want to migrate data to. For more information, see [ Creating OpenSearch Service domains](./createupdatedomains.html#createdomains) and [Creating collections](./serverless-manage.html#serverless-create). @@ -88 +87,0 @@ You can also migrate data from a source OpenSearch or Elasticsearch cluster to a - sts_role_arn: "arn:aws:iam::account-id:role/pipeline-role" @@ -99 +98 @@ You can also migrate data from a source OpenSearch or Elasticsearch cluster to a - bucket: "amzn-s3-demo-bucket" + bucket: "bucket-name" @@ -102 +100,0 @@ You can also migrate data from a source OpenSearch or Elasticsearch cluster to a - sts_role_arn: "arn:aws:iam::account-id:role/pipeline-role" @@ -109 +106,0 @@ You can also migrate data from a source OpenSearch or Elasticsearch cluster to a - sts_role_arn: "arn:aws:iam::account-id:role/pipeline-role" @@ -112 +109 @@ You can also migrate data from a source OpenSearch or Elasticsearch cluster to a -You can use a preconfigured blueprint to create this pipeline. For more information, see [Using blueprints to create a pipeline](./pipeline-blueprint.html). +You can use a preconfigured blueprint to create this pipeline. For more information, see [Working with blueprints](./pipeline-blueprint.html). @@ -114 +111 @@ You can use a preconfigured blueprint to create this pipeline. For more informat -## Connectivity to OpenSearch clusters in a VPC +## Migrating data from OpenSearch clusters in a VPC @@ -132 +129 @@ Before you create your OpenSearch Ingestion pipeline, perform the following step -If you're using the AWS Management Console to create your pipeline, you must also attach your OpenSearch Ingestion pipeline to your VPC in order to use self-managed OpenSearch or Elasticsearch. To do so, find the **Network configuration** section, select the **Attach to VPC** checkbox, and choose your CIDR from one of the provided default options, or select your own. You can use any CIDR from a private address space as defined in the [RFC 1918 Best Current Practice](https://datatracker.ietf.org/doc/html/rfc1918). +If you're using the AWS Management Console to create your pipeline, you must also attach your OpenSearch Ingestion pipeline to your VPC in order to use self-managed OpenSearch or Elasticsearch. To do so, find the **Source network options** section, select the **Attach to VPC** checkbox, and choose your CIDR from one of the provided default options. You can use any CIDR from a private address space as defined in the [RFC 1918 Best Current Practice](https://datatracker.ietf.org/doc/html/rfc1918). @@ -258 +254,0 @@ You can also migrate data from a source OpenSearch or Elasticsearch cluster to a - sts_role_arn: "arn:aws:iam::account-id:role/pipeline-role" @@ -269 +265 @@ You can also migrate data from a source OpenSearch or Elasticsearch cluster to a - bucket: "amzn-s3-demo-bucket" + bucket: "bucket-name" @@ -272 +267,0 @@ You can also migrate data from a source OpenSearch or Elasticsearch cluster to a - sts_role_arn: "arn:aws:iam::account-id:role/pipeline-role" @@ -279 +273,0 @@ You can also migrate data from a source OpenSearch or Elasticsearch cluster to a - sts_role_arn: "arn:aws:iam::account-id:role/pipeline-role" @@ -282 +276 @@ You can also migrate data from a source OpenSearch or Elasticsearch cluster to a -You can use a preconfigured blueprint to create this pipeline. For more information, see [Using blueprints to create a pipeline](./pipeline-blueprint.html). +You can use a preconfigured blueprint to create this pipeline. For more information, see [Working with blueprints](./pipeline-blueprint.html).