How Amazon Q Business connector crawls Jira ACLs
Connectors support crawl ACL and identity information where applicable based on the data source. If you index documents without ACLs, all documents are considered public. Indexing documents with ACLs ensures data security.
Amazon Q Business supports crawling ACLs for document security by default. Turning off ACLs and identity crawling are no longer supported. In preparation for connecting Amazon Q Business applications to IAM Identity Center, enable ACL indexing and identity crawling for secure querying and re-sync your connector. Once you turn ACL and identity crawling on you won't be able to turn them off.
If you want to index documents without ACLs, ensure that the documents are marked as public in your data source.
When you connect an Jira data source to Amazon Q Business, Amazon Q Business crawls ACL information attached to a document (user and group information) from your Jira instance. If you choose to activate ACL crawling, the information can be used to filter chat responses to your end user's document access level.
The Jira user IDs are mapped as follows:
-
_user_id—User IDs exist in Jira on files where there are set access permissions. They are mapped from the user emails as the user IDs in Jira.
For more information, see:
