AWS Security ChangesHomeSearch

AWS amazonq documentation change

Service: amazonq · 2025-03-19 · Documentation low

File: amazonq/latest/qbusiness-ug/servicenow-connector.md

Summary

Removed statements about unsupported access controls, user criteria, and role limitations

Security assessment

Change removes documentation of limitations but does not explicitly address security vulnerabilities or add security content

Diff

diff --git a/amazonq/latest/qbusiness-ug/servicenow-connector.md b/amazonq/latest/qbusiness-ug/servicenow-connector.md
index 2f63930d9..33d3a09a1 100644
--- a/amazonq/latest/qbusiness-ug/servicenow-connector.md
+++ b/amazonq/latest/qbusiness-ug/servicenow-connector.md
@@ -53 +53 @@ The ServiceNow Online connector has the following known limitations:
-  * There is no REST API to wake up your ServiceNow instance. To activate it when it's in hibernation mode, log in to the your ServiceNow instance.
+  * There is no REST API to wake up your ServiceNow Instance. You have to manually login into the ServiceNow instance to activate it when it's in hibernating mode.
@@ -57,10 +56,0 @@ The ServiceNow Online connector has the following known limitations:
-  * We don't support ServiceNow access controls.
-
-  * We don't support ServiceNow user criteria.
-
-  * Only the following ServiceNow roles are supported for incidents: 
-
-    * ITIL: This role provides broad access to incident management functionality.
-
-    * Custom roles: You can create custom roles with specific incident access permissions.
-