AWS Security ChangesHomeSearch

AWS amazonq documentation change

Service: amazonq · 2025-08-28 · Documentation low

File: amazonq/latest/qbusiness-ug/jira-console.md

Summary

Clarified default indexing behavior when no filters are specified

Security assessment

Improved documentation about data scope management but doesn't introduce new security features or address vulnerabilities. Highlights potential data exposure risks through default behavior.

Diff

diff --git a/amazonq/latest/qbusiness-ug/jira-console.md b/amazonq/latest/qbusiness-ug/jira-console.md
index 1ffd89ddc..72c8bc139 100644
--- a//amazonq/latest/qbusiness-ug/jira-console.md
+++ b//amazonq/latest/qbusiness-ug/jira-console.md
@@ -67 +67 @@ For more information, see [IAM role](https://docs.aws.amazon.com/amazonq/latest/
-    3. **Additional configuration – _optional_** – Choose from the following options to limit the scope for content to be indexed. Otherwise, all content will be synced by default.
+    3. **Additional configuration – _optional_** – Choose from the following options to limit the scope for content to be indexed. If no filters are specified, all content will be synced by default.
@@ -73 +73 @@ For more information, see [IAM role](https://docs.aws.amazon.com/amazonq/latest/
-       * **Issue types** – Choose the issues types you want to index.
+       * **Issue types** – Optionally choose specific issue types to index. If no issue types are selected, all issue types will be indexed by default.