AWS opensearch-service documentation change

Service: opensearch-service · 2026-01-07 · Documentation low

File: opensearch-service/latest/developerguide/opensearch-semantic-enrichment.md

Summary

Clarified version requirements for semantic enrichment and changed 'zero impact' to 'minimal impact' on search latency. Added an index setup example linking to a blog post.

Security assessment

Changes involve feature availability clarification and performance claim adjustment. No security vulnerabilities, configurations, or features are mentioned. The added example link is for general implementation guidance.

Diff

diff --git a/opensearch-service/latest/developerguide/opensearch-semantic-enrichment.md b/opensearch-service/latest/developerguide/opensearch-semantic-enrichment.md
index 3e32cacb3..cfcce45d8 100644
--- a//opensearch-service/latest/developerguide/opensearch-semantic-enrichment.md
+++ b//opensearch-service/latest/developerguide/opensearch-semantic-enrichment.md
@@ -15 +15 @@ Automatic Semantic Enrichment solves this limitation by considering both keyword
-Automatic semantic enrichment is available for Amazon OpenSearch Service domains running version 2.19 or later with the latest service software version update.
+Automatic semantic enrichment is available for Amazon OpenSearch Service domains running version 2.19 or later. Additionally, domains with OpenSearch version 2.19 also need to be on the latest service software version update.
@@ -48 +48 @@ Semantic enrichment is configured at the index level during creation, giving you
-**Zero impact on search latency**
+**Minimal impact on search latency**
@@ -120,0 +121,4 @@ With Automatic Semantic Enrichment, you pay only for the resources your workload
+#### Index set up example
+
+For a practical example, refer to the blog post <https://docs.aws.amazon.com/opensearch-service/latest/developerguide/opensearch-semantic-enrichment.html> on index setup for product catalog search using automatic semantic enrichment. Although the blog focuses on OpenSearch Service Serverless, the approach applies to managed clusters as well. Use this example as a starting point, then test with your own workload to validate search relevance improvements.
+