AWS chatbot documentation change
Summary
Updated service name references from 'Amazon Q Developer in chat channels' to 'Amazon Q Developer in chat applications' throughout the document. Changed console references and policy examples to match new terminology.
Security assessment
Changes appear to be branding/terminology updates rather than security-related modifications. The policy enforcement mechanisms and security controls described remain functionally identical, with only service name references being updated. No new security features or vulnerability mitigations were introduced.
Diff
diff --git a/chatbot/latest/adminguide/chatbot-orgs-policy.md b/chatbot/latest/adminguide/chatbot-orgs-policy.md index 2757d8640..ad32922c1 100644 --- a//chatbot/latest/adminguide/chatbot-orgs-policy.md +++ b//chatbot/latest/adminguide/chatbot-orgs-policy.md @@ -11 +11 @@ AWS Chatbot is now Amazon Q Developer. [Learn more](./service-rename.html) -Organization administrators can manage multiple Amazon Q Developer in chat channels settings across all accounts within an organization using Amazon Q Developer in chat channels chat applications policies (chat applications policies). Chat applications policies define where Amazon Q Developer in chat channels can deliver notifications and if it can respond to Amazon Q Developer in chat channels mention events. Using chat applications policies, administrators can: +Organization administrators can manage multiple Amazon Q Developer in chat applications settings across all accounts within an organization using Amazon Q Developer in chat applications chat applications policies (chat applications policies). Chat applications policies define where Amazon Q Developer in chat applications can deliver notifications and if it can respond to Amazon Q Developer in chat applications mention events. Using chat applications policies, administrators can: @@ -24 +24 @@ Organization administrators can manage multiple Amazon Q Developer in chat chann -Chat applications policies restrict and take precedence over account level settings like [role settings](./understanding-permissions.html#role-settings) and [Channel guardrail policies](./understanding-permissions.html#channel-guardrails). Administrators can define rules in a policy and apply those rules to an entire organization or a group of accounts, referred to as OUs. For more information, see [Managing organizational units](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_ous.html) in the _AWS Organizations User Guide_. You can access and modify these policies from the Amazon Q Developer in chat channels console or the AWS Organizations console. For more information about organization policies, see [Managing policies in AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies.html) _AWS Organizations User Guide_. +Chat applications policies restrict and take precedence over account level settings like [role settings](./understanding-permissions.html#role-settings) and [Channel guardrail policies](./understanding-permissions.html#channel-guardrails). Administrators can define rules in a policy and apply those rules to an entire organization or a group of accounts, referred to as OUs. For more information, see [Managing organizational units](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_ous.html) in the _AWS Organizations User Guide_. You can access and modify these policies from the Amazon Q Developer in chat applications console or the AWS Organizations console. For more information about organization policies, see [Managing policies in AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies.html) _AWS Organizations User Guide_. @@ -30 +30 @@ If your users try to perform an action restricted by your chat applications poli -Amazon Q Developer in chat channels organization policies are validated at runtime, so existing resources are continuously checked for compliance. There is no overlap with existing IAM permissions as there aren’t currently any runtime-based IAM permissions for sending notifications or interacting with Amazon Q Developer in chat channels. +Amazon Q Developer in chat applications organization policies are validated at runtime, so existing resources are continuously checked for compliance. There is no overlap with existing IAM permissions as there aren’t currently any runtime-based IAM permissions for sending notifications or interacting with Amazon Q Developer in chat applications. @@ -44 +44 @@ Chat application policies are limited to AWS account access to Amazon Q Develope - * [Tutorial: Creating chat applications policies in Amazon Q Developer in chat channels](./org-policy-tutorial.html) + * [Tutorial: Creating chat applications policies in Amazon Q Developer in chat applications](./org-policy-tutorial.html) @@ -48 +48 @@ Chat application policies are limited to AWS account access to Amazon Q Develope - * [Deleting chat applications policies in Amazon Q Developer in chat channels](./delete-org-pol.html) + * [Deleting chat applications policies in Amazon Q Developer in chat applications](./delete-org-pol.html) @@ -55 +55 @@ Chat application policies are limited to AWS account access to Amazon Q Develope -The following policy allows restricted Amazon Q Developer in chat channels access for selected Slack workspaces and a Microsoft Teams tenant. +The following policy allows restricted Amazon Q Developer in chat applications access for selected Slack workspaces and a Microsoft Teams tenant. @@ -168 +168 @@ The following policy allows restricted Amazon Q Developer in chat channels acces - * The `default` block at the bottom sets the client to be disabled, which disables Amazon Q Developer in chat channels across the organization unless overridden at a lower level. This means Amazon Chime is disabled in this example. This default also disables any new chat platform that Amazon Q Developer in chat channels supports. For example, if Amazon Q Developer in chat channels supports a new chat platform, this default disables that newly supported chat platform as well. + * The `default` block at the bottom sets the client to be disabled, which disables Amazon Q Developer in chat applications across the organization unless overridden at a lower level. This means Amazon Chime is disabled in this example. This default also disables any new chat platform that Amazon Q Developer in chat applications supports. For example, if Amazon Q Developer in chat applications supports a new chat platform, this default disables that newly supported chat platform as well.