AWS chatbot documentation change
Summary
Updated terminology from 'chat channels' to 'chat applications' across service documentation, including policy references and console workflows. Added clarification about Free/Pro tier access limitations.
Security assessment
Changes are purely terminological updates (rebranding AWS Chatbot to Amazon Q Developer in chat contexts) with no security vulnerability fixes or security feature additions. The policy schema and access control mechanisms remain unchanged. The tier limitation clarification relates to feature availability rather than security controls.
Diff
diff --git a/chatbot/latest/adminguide/service-rename.md b/chatbot/latest/adminguide/service-rename.md index fbbc62060..ab79a1b42 100644 --- a//chatbot/latest/adminguide/service-rename.md +++ b//chatbot/latest/adminguide/service-rename.md @@ -54 +54 @@ Instead of entering `@Amazon Q`, you can enter `@Q` and choose the autocomplete -The references to AWS Chatbot in the AWS Management Console are updated with the name Amazon Q Developer in chat channels. The workflows to create and manage chat configurations remain unchanged in the renamed console. +The references to AWS Chatbot in the AWS Management Console are updated with the name Amazon Q Developer in chat applications. The workflows to create and manage chat configurations remain unchanged in the renamed console. @@ -58 +58 @@ The references to AWS Chatbot in the AWS Management Console are updated with the -AWS Chatbot organization policies (Chatbot policies) are now called Amazon Q Developer in chat channels policies (chat applications policies). These policies allow you to control access to an organization’s accounts from chat applications like Microsoft Teams and Slack. For more information, see [Amazon Q Developer in chat channels organization policies](https://docs.aws.amazon.com/chatbot/latest/adminguide/chatbot-orgs-policy.html). The schema for the chat application policy remains unchanged. Your existing policies will continue to function as is. +AWS Chatbot organization policies (Chatbot policies) are now called Amazon Q Developer in chat applications policies (chat applications policies). These policies allow you to control access to an organization’s accounts from chat applications like Microsoft Teams and Slack. For more information, see [Amazon Q Developer in chat applications organization policies](https://docs.aws.amazon.com/chatbot/latest/adminguide/chatbot-orgs-policy.html). The schema for the chat application policy remains unchanged. Your existing policies will continue to function as is. @@ -76 +76 @@ Your existing chat configurations in the chat applications will continue to work - * AWS Organizations Service control policies (SCPs) and chatbot management policies (now called Amazon Q Developer in chat channels policies) + * AWS Organizations Service control policies (SCPs) and chatbot management policies (now called Amazon Q Developer in chat applications policies) @@ -85 +85 @@ Your existing chat configurations in the chat applications will continue to work -There is no change to your current usage and pricing. Non-generative AI features for sending notifications and running CLI-based commands using action buttons, aliases, and typed-commands are still available to you at no additional cost after the renaming. When you use Amazon Q Developer in chat channels, access is limited to the Amazon Q Developer Free tier, even when you are subscribed to Amazon Q Developer Pro tier. This update doesn't automatically enable identity-aware sessions, which are needed to chat with Amazon Q Developer at the Pro tier. For more information, see [Amazon Q Developer pricing](https://aws.amazon.com/q/developer/pricing/). +There is no change to your current usage and pricing. Non-generative AI features for sending notifications and running CLI-based commands using action buttons, aliases, and typed-commands are still available to you at no additional cost after the renaming. When you use Amazon Q Developer in chat applications, access is limited to the Amazon Q Developer Free tier, even when you are subscribed to Amazon Q Developer Pro tier. This update doesn't automatically enable identity-aware sessions, which are needed to chat with Amazon Q Developer at the Pro tier. For more information, see [Amazon Q Developer pricing](https://aws.amazon.com/q/developer/pricing/).