AWS chatbot documentation change
Summary
Updated terminology from 'chat channels' to 'chat applications' throughout the documentation, including references to Amazon Q Developer integration and IAM policy configuration steps.
Security assessment
Changes are purely terminological (channels→applications) with no modifications to security-related content. The existing references to IAM policies (AIOpsOperatorAccess) and permissions remain unchanged in substance. No vulnerabilities, security controls, or incident response procedures were added/modified.
Diff
diff --git a/chatbot/latest/adminguide/config-cbt-investigations.md b/chatbot/latest/adminguide/config-cbt-investigations.md index 3df2d64d3..f66eb470c 100644 --- a//chatbot/latest/adminguide/config-cbt-investigations.md +++ b//chatbot/latest/adminguide/config-cbt-investigations.md @@ -5 +5 @@ -Step 1: Connecting Amazon Q Developer in chat channels with an investigation group +Step 1: Connecting Amazon Q Developer in chat applications with an investigation group @@ -11 +11 @@ AWS Chatbot is now Amazon Q Developer. [Learn more](./service-rename.html) -To set up Amazon Q operational investigations in your chat applications, you must add the following policies to enable two-way communication between investigations and Amazon Q Developer in chat channels. You can add these policies during step 2 of the Amazon Q Developer in chat channels channel configuration process for [Slack](./slack-setup.html#slack-client-setup2) and [Microsoft Teams](./teams-setup.html#teams-client-setup-2) when you define your user permissions or by editing your configurations' **Permissions** in the Amazon Q Developer in chat channels console. +To set up Amazon Q operational investigations in your chat applications, you must add the following policies to enable two-way communication between investigations and Amazon Q Developer in chat applications. You can add these policies during step 2 of the Amazon Q Developer in chat applications channel configuration process for [Slack](./slack-setup.html#slack-client-setup2) and [Microsoft Teams](./teams-setup.html#teams-client-setup-2) when you define your user permissions or by editing your configurations' **Permissions** in the Amazon Q Developer in chat applications console. @@ -15 +15 @@ To set up Amazon Q operational investigations in your chat applications, you mus - * Attach the **AIOpsOperatorAccess** managed IAM policy to your guardrail policies in Amazon Q Developer in chat channels. This grants permissions to Amazon Q Developer in chat channels to interact with Amazon Q operational investigations and perform required actions on your behalf. + * Attach the **AIOpsOperatorAccess** managed IAM policy to your guardrail policies in Amazon Q Developer in chat applications. This grants permissions to Amazon Q Developer in chat applications to interact with Amazon Q operational investigations and perform required actions on your behalf. @@ -20 +20 @@ To set up Amazon Q operational investigations in your chat applications, you mus -## Step 1: Connecting Amazon Q Developer in chat channels with an investigation group +## Step 1: Connecting Amazon Q Developer in chat applications with an investigation group @@ -28 +28 @@ You can make investigations in your chat channels easier by adding [custom actio -###### To connect Amazon Q Developer in chat channels with an investigation group +###### To connect Amazon Q Developer in chat applications with an investigation group @@ -36 +36 @@ You can make investigations in your chat channels easier by adding [custom actio -When selecting an Amazon SNS topic, select the same topic configured in your Amazon Q Developer in chat channels channel configuration. +When selecting an Amazon SNS topic, select the same topic configured in your Amazon Q Developer in chat applications channel configuration.