AWS chatbot documentation change
Summary
Updated terminology from 'chat channels' to 'chat applications' throughout the document to align with product renaming (AWS Chatbot to Amazon Q Developer)
Security assessment
Changes are purely branding/terminology updates (AWS Chatbot → Amazon Q Developer) and replacing 'chat channels' with 'chat applications'. No security vulnerabilities, configurations, or features are mentioned or modified in the content.
Diff
diff --git a/chatbot/latest/adminguide/test-notifications-cw.md b/chatbot/latest/adminguide/test-notifications-cw.md index f6e82ec44..476614e4c 100644 --- a//chatbot/latest/adminguide/test-notifications-cw.md +++ b//chatbot/latest/adminguide/test-notifications-cw.md @@ -9 +9 @@ AWS Chatbot is now Amazon Q Developer. [Learn more](./service-rename.html) -To verify that an Amazon Simple Notification Service (Amazon SNS) topic sends notifications to your chat channels, you can test your setup by sending a notification. Any SNS topic can send notifications to your chat channels, but the topic must be assigned to a service supported by Amazon Q Developer in chat channels. For more information about supported services, see [Supported services for Amazon Q Developer in chat applications](./chatbot-services.html). +To verify that an Amazon Simple Notification Service (Amazon SNS) topic sends notifications to your chat channels, you can test your setup by sending a notification. Any SNS topic can send notifications to your chat channels, but the topic must be assigned to a service supported by Amazon Q Developer in chat applications. For more information about supported services, see [Supported services for Amazon Q Developer in chat applications](./chatbot-services.html). @@ -13 +13 @@ To verify that an Amazon Simple Notification Service (Amazon SNS) topic sends no -CloudWatch alarms and events are separately configured and have different characteristics for use with Amazon Q Developer in chat channels. +CloudWatch alarms and events are separately configured and have different characteristics for use with Amazon Q Developer in chat applications. @@ -15 +15 @@ CloudWatch alarms and events are separately configured and have different charac -The following procedure uses a CloudWatch alarm because most AWS services supported by Amazon Q Developer in chat channels send their event and alarm data to CloudWatch. +The following procedure uses a CloudWatch alarm because most AWS services supported by Amazon Q Developer in chat applications send their event and alarm data to CloudWatch. @@ -17 +17 @@ The following procedure uses a CloudWatch alarm because most AWS services suppor -You configure CloudWatch alarms using performance metrics from the services that are active in your account. When you associate CloudWatch alarms with an Amazon SNS topic that is mapped to Amazon Q Developer in chat channels, the Amazon SNS topic sends the CloudWatch alarm notifications to the chat channels. For more information, see [Monitoring AWS services using Amazon Q Developer in chat channels](./related-services.html) and the [Troubleshooting](./chatbot-troubleshooting.html) topic. +You configure CloudWatch alarms using performance metrics from the services that are active in your account. When you associate CloudWatch alarms with an Amazon SNS topic that is mapped to Amazon Q Developer in chat applications, the Amazon SNS topic sends the CloudWatch alarm notifications to the chat channels. For more information, see [Monitoring AWS services using Amazon Q Developer in chat applications](./related-services.html) and the [Troubleshooting](./chatbot-troubleshooting.html) topic. @@ -25 +25 @@ You configure CloudWatch alarms using performance metrics from the services that - 3. Select the correct AWS **Region** at the top right of the AWS console, that contains the Amazon SNS topic you need. (**Tip:** to make sure you have the right Region for your SNS topics for testing alarms, you can check the Amazon Q Developer in chat channels configuration to see the regions for all configured SNS topics in each channel or webhook.) + 3. Select the correct AWS **Region** at the top right of the AWS console, that contains the Amazon SNS topic you need. (**Tip:** to make sure you have the right Region for your SNS topics for testing alarms, you can check the Amazon Q Developer in chat applications configuration to see the regions for all configured SNS topics in each channel or webhook.) @@ -31 +31 @@ You configure CloudWatch alarms using performance metrics from the services that - 2. Choose the check box for the SNS topic next to its **Topic Name** and **Metric Name**. Any SNS topics that you configured with Amazon Q Developer in chat channels appear in this list. + 2. Choose the check box for the SNS topic next to its **Topic Name** and **Metric Name**. Any SNS topics that you configured with Amazon Q Developer in chat applications appear in this list. @@ -63 +63 @@ For **Notification** , choose the following options. - 3. For **Send a notification to...** , choose your SNS topic that has a subscription to Amazon Q Developer in chat channels. If the SNS topic is subscribed in Amazon Q Developer in chat channels, the endpoint value for Amazon Q Developer in chat channels appears in the **Email (endpoints)** field. + 3. For **Send a notification to...** , choose your SNS topic that has a subscription to Amazon Q Developer in chat applications. If the SNS topic is subscribed in Amazon Q Developer in chat applications, the endpoint value for Amazon Q Developer in chat applications appears in the **Email (endpoints)** field. @@ -67 +67 @@ For **Notification** , choose the following options. -If the endpoint value doesn't appear in the **Email (endpoints)** field, make sure that the SNS topic is set up correctly in the Microsoft Teams channel, Slack channel or Amazon Chime webhook. For more information, see [Setting up Amazon Q Developer in chat channels with Microsoft Teams](./teams-setup.html), [Setting up Amazon Q Developer in chat channels with Slack](./slack-setup.html), or [Setting up Amazon Q Developer in chat channels with Amazon Chime](./chime-setup.html). +If the endpoint value doesn't appear in the **Email (endpoints)** field, make sure that the SNS topic is set up correctly in the Microsoft Teams channel, Slack channel or Amazon Chime webhook. For more information, see [Setting up Amazon Q Developer in chat applications with Microsoft Teams](./teams-setup.html), [Setting up Amazon Q Developer in chat applications with Slack](./slack-setup.html), or [Setting up Amazon Q Developer in chat applications with Amazon Chime](./chime-setup.html). @@ -78 +78 @@ If the endpoint value doesn't appear in the **Email (endpoints)** field, make su -When the alarm triggers for the first time, you should receive the first test notification in your chat room, confirming that Amazon Q Developer in chat channels is working correctly and receiving alarm notifications from Amazon CloudWatch. +When the alarm triggers for the first time, you should receive the first test notification in your chat room, confirming that Amazon Q Developer in chat applications is working correctly and receiving alarm notifications from Amazon CloudWatch.