AWS Security ChangesHomeSearch

AWS opensearch-service medium security documentation change

Service: opensearch-service · 2026-05-16 · Security-related medium

File: opensearch-service/latest/developerguide/configure-client-self-managed-opensearch.md

Summary

Updated VPC CIDR requirement to /24 prefix length in two places

Security assessment

Consistent enforcement of /24 CIDR blocks across all network configuration steps improves baseline security by reducing potential misconfigurations that could expose broader network segments than intended.

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 e68e7238a..cc378aeee 100644
--- a//opensearch-service/latest/developerguide/configure-client-self-managed-opensearch.md
+++ b//opensearch-service/latest/developerguide/configure-client-self-managed-opensearch.md
@@ -134 +134 @@ Before you create your OpenSearch Ingestion pipeline, perform the following step
-  4. Obtain the ID of the VPC that that has access to self-managed OpenSearch or Elasticsearch. Choose the VPC CIDR to be used by OpenSearch Ingestion.
+  4. Obtain the ID of the VPC that that has access to self-managed OpenSearch or Elasticsearch. Choose the /24 VPC CIDR block to be used by OpenSearch Ingestion.
@@ -138 +138 @@ 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 **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).
+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. The CIDR block must use a /24 prefix length. You can use any /24 CIDR from a private address space as defined in the [RFC 1918 Best Current Practice](https://datatracker.ietf.org/doc/html/rfc1918).