AWS connect documentation change
Summary
Renamed 'Amazon Q in Connect Assistants' to 'Connect AI agents Assistants' in section headers and descriptions
Security assessment
Terminology update without security implications. Changes involve rebranding (Amazon Q → AI agents) but maintain identical policy functionality and security posture. No evidence of vulnerability fixes.
Diff
diff --git a/connect/latest/adminguide/security_iam_id-based-policy-examples.md b/connect/latest/adminguide/security_iam_id-based-policy-examples.md index 683293def..02f62ab0f 100644 --- a//connect/latest/adminguide/security_iam_id-based-policy-examples.md +++ b//connect/latest/adminguide/security_iam_id-based-policy-examples.md @@ -5 +5 @@ -Policy best practicesAllow IAM users to view their own permissionsGrant "View User" permissionsAllow users to integrate with external applicationsDescribe and update Amazon Connect users based on tagsCreate Amazon Connect users based on tagsCreate and view Amazon AppIntegrations resourcesCreate and view Amazon Q in Connect AssistantsManage outbound campaigns resources +Policy best practicesAllow IAM users to view their own permissionsGrant "View User" permissionsAllow users to integrate with external applicationsDescribe and update Amazon Connect users based on tagsCreate Amazon Connect users based on tagsCreate and view Amazon AppIntegrations resourcesCreate and view Connect AI agents AssistantsManage outbound campaigns resources @@ -29 +29 @@ To learn how to create an IAM identity-based policy using these example JSON pol - * Create and view Amazon Q in Connect Assistants + * Create and view Connect AI agents Assistants @@ -259 +259 @@ JSON -## Create and view Amazon Q in Connect Assistants +## Create and view Connect AI agents Assistants @@ -261 +261 @@ JSON -The following sample policy allows Amazon Q in Connect assistants to be created, listed, fetched, and deleted. +The following sample policy allows Connect AI agents assistants to be created, listed, fetched, and deleted.