AWS amazonq documentation change
Summary
Relocated ServiceNow connector limitations to external page and cleaned up content
Security assessment
The change removes details about security limitations (e.g., lack of access control support) from the main document but maintains them elsewhere. This is a structural documentation change rather than a security update.
Diff
diff --git a/amazonq/latest/qbusiness-ug/servicenow-connector.md b/amazonq/latest/qbusiness-ug/servicenow-connector.md index b3ff149bd..b35d4fe64 100644 --- a//amazonq/latest/qbusiness-ug/servicenow-connector.md +++ b//amazonq/latest/qbusiness-ug/servicenow-connector.md @@ -5,2 +4,0 @@ -Known limitations - @@ -13 +11 @@ ServiceNow provides a cloud-based service management system to create and manage - * Known limitations for the Amazon Q Business ServiceNow Online connector + * [Known limitations for the Amazon Q Business ServiceNow Online connector](./servicenow-limitations.html) @@ -49,21 +46,0 @@ ServiceNow provides a cloud-based service management system to create and manage -## Known limitations for the Amazon Q Business ServiceNow Online connector - -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. - - * Because Amazon Q Business uses email address as unique identifiers, each user must have a unique email address. - - * 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. - - - - @@ -78 +55 @@ Error Codes -Overview +Known limitations