AWS Security ChangesHomeSearch

AWS amazonq documentation change

Service: amazonq · 2025-07-18 · Documentation low

File: amazonq/latest/qbusiness-ug/setting-relevancy-preferences.md

Summary

Updated AWS CLI examples by replacing placeholder syntax and standardizing data source ID references.

Security assessment

Changes involve example syntax corrections and placeholder standardization without any security-specific context or vulnerability fixes.

Diff

diff --git a/amazonq/latest/qbusiness-ug/setting-relevancy-preferences.md b/amazonq/latest/qbusiness-ug/setting-relevancy-preferences.md
index ecced1a08..0ade4f0f4 100644
--- a//amazonq/latest/qbusiness-ug/setting-relevancy-preferences.md
+++ b//amazonq/latest/qbusiness-ug/setting-relevancy-preferences.md
@@ -36 +36 @@ AWS CLI
-This example shows how to increase the relevancy based on the `_last_update_at` metadata field. 
+This example shows how to increase the relevancy based on the `_last_update_at` metadata field. In this example, replace each `user input placeholder` with your own information:
@@ -39,3 +39,3 @@ This example shows how to increase the relevancy based on the `_last_update_at`
-    aws qbusiness --region >region< update-retriever \
-      --application-id >application_id< \
-      --retriever-id >retriever_id< \
+    aws qbusiness --region region update-retriever \
+      --application-id application_id \
+      --retriever-id retriever_id \
@@ -44 +44 @@ This example shows how to increase the relevancy based on the `_last_update_at`
-            "indexId": ">index_id<",
+            "indexId": "index_id",
@@ -49 +49 @@ This example shows how to increase the relevancy based on the `_last_update_at`
-                  "boostingDurationInSeconds": <long<
+                  "boostingDurationInSeconds": long;
@@ -56,2 +56,2 @@ This example shows how to increase the relevancy based on the `_last_update_at`
-                    "<data_source_id_1>": "ONE"|"TWO"|"THREE"|"FOUR"|"FIVE",
-                    "<data_source_id_1>": "ONE"|"TWO"|"THREE"|"FOUR"|"FIVE",
+                    "data_source_id_1": "ONE"|"TWO"|"THREE"|"FOUR"|"FIVE",
+                    "data_source_id_1": "ONE"|"TWO"|"THREE"|"FOUR"|"FIVE",
@@ -67 +67 @@ This example shows how to increase the relevancy based on the `_last_update_at`
-This example shows an example input.
+This example shows an example input. Replace each `user input placeholder` with your own information:
@@ -71,3 +71,3 @@ This example shows an example input.
-      --endpoint-url https://frontend.us-west-2.gamma.plato.ai.aws.dev --no-verify-ssl \
-      --application-id 0fc4e455-9a43-47e7-8b43-6f3ed9dd4e8a \
-      --retriever-id 97a301c6-4824-439a-b162-32a2df59ea17 \
+      --endpoint-url https://endpoint-url --no-verify-ssl \
+      --application-id application_id
+      --retriever-id retriever_id \
@@ -76 +76 @@ This example shows an example input.
-            "indexId": "38452016-2247-4058-9549-0bfa804ad78d",
+            "indexId": "index_id",
@@ -88,5 +88,5 @@ This example shows an example input.
-                    "14eafa2a-314d-44c2-acc1-9f12140d193e": "ONE",
-                    "86b24a49-f789-410a-97bb-32b49f4bc1c0": "TWO",
-                    "14eafa2a-314d-44c2-acc1-9f12140d193": "THREE",
-                    "86b24a49-f789-410a-97bb-32b49f4bc1c": "FOUR",
-                    "14eafa2a-314d-44c2-acc1-9f12140d19": "FIVE"
+                    "data_source_id_1": "ONE",
+                    "data_source_id_1": "TWO",
+                    "data_source_id_1": "THREE",
+                    "data_source_id_1": "FOUR",
+                    "data_source_id_1": "FIVE"