AWS chatbot documentation change
Summary
Updated documentation to reflect service name change from 'Amazon Q Developer' to 'Amazon Q Developer in chat channels' throughout the file. Added clarification about IAM policy requirements for investigation group communication.
Security assessment
Changes primarily involve service renaming and clarifying existing IAM policy requirements. No new security controls or vulnerabilities addressed. The mention of AIOpsOperatorAccess policy is part of existing guardrail configuration, not a new security feature.
Diff
diff --git a/chatbot/latest/adminguide/config-cbt-investigations.md b/chatbot/latest/adminguide/config-cbt-investigations.md index 9f46887e5..3df2d64d3 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 with an investigation group +Step 1: Connecting Amazon Q Developer in chat channels 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. You can add these policies during step 2 of the Amazon Q Developer 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 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 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. @@ -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. This grants permissions to Amazon Q Developer 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 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. @@ -20 +20 @@ To set up Amazon Q operational investigations in your chat applications, you mus -## Step 1: Connecting Amazon Q Developer with an investigation group +## Step 1: Connecting Amazon Q Developer in chat channels with an investigation group @@ -28 +28 @@ You can make investigations in your chat channels easier by adding [custom actio -###### To connect Amazon Q Developer with an investigation group +###### To connect Amazon Q Developer in chat channels 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 channel configuration. +When selecting an Amazon SNS topic, select the same topic configured in your Amazon Q Developer in chat channels channel configuration.