AWS chatbot documentation change
Summary
Updated service name references from 'Amazon Q Developer' to 'Amazon Q Developer in chat channels', removed section about generative AI features requiring IAM policy, and adjusted policy naming conventions
Security assessment
The changes primarily focus on branding updates (name changes) and documentation structure. The removed section about requiring the AmazonQDeveloperAccess managed policy for generative AI features could be considered a security-related removal, but there's no evidence this reflects a resolved vulnerability or new security concern. The policy schema remains unchanged and existing policies continue functioning.
Diff
diff --git a/chatbot/latest/adminguide/service-rename.md b/chatbot/latest/adminguide/service-rename.md index b035a3eba..fbbc62060 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. 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 channels. 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 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 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 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. @@ -64,6 +63,0 @@ With this launch, the setting to manage how AWS uses your content in chat applic -### Generative AI-powered assistant in chat applications - -To use generative AI features, you must add the `[AmazonQDeveloperAccess](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/managed-policy.html#amazonq-policy-developeraccess)` managed policy to your IAM role and channel guardrails. - -Amazon Q Developer generative AI features are available in chat applications at no additional cost. You can chat with the generative AI assistant in your chat channels about the state of your resources, diagnose issues, explain billing and account costs, and receive guidance to remediate issues based on AWS best practices. - @@ -82 +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 policies) + * AWS Organizations Service control policies (SCPs) and chatbot management policies (now called Amazon Q Developer in chat channels policies) @@ -91 +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, 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 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/).