Prerequisites for connecting Amazon Q Business to Slack

Before you begin, make sure that you have completed the following prerequisites.

In Slack, make sure you have:

• Created a Slack Bot User OAuth token or Slack User OAuth token. You can choose either token to connect Amazon Q to your Slack data source. See Slack documentation on access tokens for more information.

  Note

  If you use the bot token as part of your Slack credentials, you cannot index direct messages and group messages. You must add the bot token to the channel you want to index.

• Noted your Slack workspace team ID from your Slack workspace main page URL. For example, https://app.slack.com/client/T0123456789/... where T0123456789 is the team ID.

• Added the following Oauth scopes/ read permissions:

  User token scope	Bot token scope
  channels:history channels:read emoji:read files:read groups:history groups:read im:history im:read mpim:history mpim:read team:read users.profile:read users:read users:read.email	channels:history channels:manage channels:read channels:read conversations.connect:manage conversations.connect:read files:read groups:history groups:read im:history im:read mpim:history mpim:read reactions:read team:read usergroups:read users.profile:read users:read users:read.email

In your AWS account, make sure you have:

• Created an IAM role for your data source and, if using the Amazon Q API, noted the ARN of the IAM role.

• Stored your Slack authentication credentials in an AWS Secrets Manager secret and, if using the Amazon Q API, noted the ARN of the secret.

  Note

  If you’re a console user, you can create the IAM role and Secrets Manager secret as part of configuring your Amazon Q application on the console.

For a list of things to consider while configuring your data source, see Data source connector configuration best practices.