AWS connect documentation change
Summary
Renamed 'Amazon Connect' to 'Connect Customer' throughout the document and updated policy examples to reference 'Connect Customer users' instead of 'Amazon Connect users'
Security assessment
The changes appear to be branding/naming convention updates only. No security vulnerabilities are mentioned, no policy logic is modified, and no new security guidance is added. The updates maintain existing IAM policy examples with new terminology but don't alter security implications.
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 6c19081d8..d72590769 100644 --- a//connect/latest/adminguide/security_iam_id-based-policy-examples.md +++ b//connect/latest/adminguide/security_iam_id-based-policy-examples.md @@ -7 +7 @@ -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 +Policy best practicesAllow IAM users to view their own permissionsGrant "View User" permissionsAllow users to integrate with external applicationsDescribe and update Connect Customer users based on tagsCreate Connect Customer users based on tagsCreate and view Amazon AppIntegrations resourcesCreate and view Connect AI agents AssistantsManage outbound campaigns resources @@ -9 +9 @@ Policy best practicesAllow IAM users to view their own permissionsGrant "View Us -# Amazon Connect identity-based policy examples +# Connect Customer identity-based policy examples @@ -11 +11 @@ Policy best practicesAllow IAM users to view their own permissionsGrant "View Us -By default, IAM entities don't have permission to create or modify Amazon Connect resources. They also can't perform tasks using the AWS Management Console, AWS CLI, or AWS API. An IAM administrator must create IAM policies that grant IAM entities permission to perform specific API operations on the specified resources they need. The IAM administrator must then attach those policies to the IAM entities that require those permissions. +By default, IAM entities don't have permission to create or modify Connect Customer resources. They also can't perform tasks using the AWS Management Console, AWS CLI, or AWS API. An IAM administrator must create IAM policies that grant IAM entities permission to perform specific API operations on the specified resources they need. The IAM administrator must then attach those policies to the IAM entities that require those permissions. @@ -25 +25 @@ To learn how to create an IAM identity-based policy using these example JSON pol - * Describe and update Amazon Connect users based on tags + * Describe and update Connect Customer users based on tags @@ -27 +27 @@ To learn how to create an IAM identity-based policy using these example JSON pol - * Create Amazon Connect users based on tags + * Create Connect Customer users based on tags @@ -40 +40 @@ To learn how to create an IAM identity-based policy using these example JSON pol -Identity-based policies determine whether someone can create, access, or delete Amazon Connect resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: +Identity-based policies determine whether someone can create, access, or delete Connect Customer resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: @@ -99 +99 @@ When you create a user or [group](https://docs.aws.amazon.com/IAM/latest/UserGui -For example, imagine you have a group of entry-level developers. You can create an IAM group named `Junior application developers`, and include all entry-level developers. Then, associate a policy with that group that grants them permissions to view Amazon Connect users. In this scenario, you might have a policy such as the following sample. +For example, imagine you have a group of entry-level developers. You can create an IAM group named `Junior application developers`, and include all entry-level developers. Then, associate a policy with that group that grants them permissions to view Connect Customer users. In this scenario, you might have a policy such as the following sample. @@ -164 +164 @@ JSON -## Describe and update Amazon Connect users based on tags +## Describe and update Connect Customer users based on tags @@ -166 +166 @@ JSON -In an IAM policy, you can optionally specify conditions that control when a policy is in effect. For example, you can define a policy that allows users to update only an Amazon Connect user who is working in the test environment. +In an IAM policy, you can optionally specify conditions that control when a policy is in effect. For example, you can define a policy that allows users to update only an Connect Customer user who is working in the test environment. @@ -168 +168 @@ In an IAM policy, you can optionally specify conditions that control when a poli -You can define some conditions that are specific to Amazon Connect, and define other conditions that apply to all of AWS. For more information and a list of AWS-wide conditions, see Condition in [IAM JSON Policy Elements Reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html#Condition) in the _IAM User Guide_. +You can define some conditions that are specific to Connect Customer, and define other conditions that apply to all of AWS. For more information and a list of AWS-wide conditions, see Condition in [IAM JSON Policy Elements Reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html#Condition) in the _IAM User Guide_. @@ -199 +199 @@ JSON -This policy allows "describe user" and "update user" but only for those Amazon Connect users tagged with tag "Department: Test" where "Department" is the tag key and "Test" is the tag value. +This policy allows "describe user" and "update user" but only for those Connect Customer users tagged with tag "Department: Test" where "Department" is the tag key and "Test" is the tag value. @@ -201 +201 @@ This policy allows "describe user" and "update user" but only for those Amazon C -## Create Amazon Connect users based on tags +## Create Connect Customer users based on tags @@ -315 +315 @@ JSON -Onboarding permissions: The following sample policy allows Amazon Connect instances to be onboarded to outbound campaigns. +Onboarding permissions: The following sample policy allows Connect Customer instances to be onboarded to outbound campaigns. @@ -440 +440 @@ ReadOnly permissions: The following sample policy allows read-only access to the -Tag-based permissions: The following sample policy restricts access to the campaigns integrated with a particular Amazon Connect instance using tags. More permissions can be added based on the use case. +Tag-based permissions: The following sample policy restricts access to the campaigns integrated with a particular Connect Customer instance using tags. More permissions can be added based on the use case. @@ -468 +468 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -How Amazon Connect works with IAM +How Connect Customer works with IAM