AWS connect documentation change
Summary
Renamed 'Amazon Connect' to 'Connect Customer' throughout the documentation
Security assessment
The changes are purely branding/naming updates replacing 'Amazon Connect' with 'Connect Customer'. No security controls, configurations, or vulnerabilities are modified. The technical content about tag-based access control remains unchanged.
Diff
diff --git a/connect/latest/adminguide/tag-based-access-control.md b/connect/latest/adminguide/tag-based-access-control.md index a79a1f660..e5d1c0aec 100644 --- a//connect/latest/adminguide/tag-based-access-control.md +++ b//connect/latest/adminguide/tag-based-access-control.md @@ -7 +7 @@ -Apply tag-based access control using the API/SDKApply tag-based access control using the Amazon Connect admin websiteConfiguration limitationsBest practices +Apply tag-based access control using the API/SDKApply tag-based access control using the Connect Customer admin websiteConfiguration limitationsBest practices @@ -9 +9 @@ Apply tag-based access control using the API/SDKApply tag-based access control u -# Apply tag-based access control in Amazon Connect +# Apply tag-based access control in Connect Customer @@ -11 +11 @@ Apply tag-based access control using the API/SDKApply tag-based access control u -You use tag-based access controls to configure granular access to specific resources based on assigned resource tags. You can configure tag-based access controls by using the API/SDK or the Amazon Connect admin website for supported resources. +You use tag-based access controls to configure granular access to specific resources based on assigned resource tags. You can configure tag-based access controls by using the API/SDK or the Connect Customer admin website for supported resources. @@ -19 +19 @@ For more detailed information on tag-based access control, see [Controlling acce -## Apply tag-based access control using the Amazon Connect admin website +## Apply tag-based access control using the Connect Customer admin website @@ -21 +21 @@ For more detailed information on tag-based access control, see [Controlling acce -A _resource_ tag is a custom metadata label that you can add to a resource in order to make it easier to identify, organize, and find in a search. You can apply tags programmatically using the Amazon Connect SDK/APIs, and for certain resources you can apply tags from within the Amazon Connect console. To learn more about resource tags, see [Add tags to resources in Amazon Connect](./tagging.html). +A _resource_ tag is a custom metadata label that you can add to a resource in order to make it easier to identify, organize, and find in a search. You can apply tags programmatically using the Connect Customer SDK/APIs, and for certain resources you can apply tags from within the Connect Customer console. To learn more about resource tags, see [Add tags to resources in Connect Customer](./tagging.html). @@ -25 +25 @@ An access control tag is similar to a resource tag in that it uses the same _Key -To use tags to control access to resources within the admin website of your Amazon Connect instance, you need to configure the access control section within a given security profile. For example, to control access to a routing profile based on the tags you've assigned to it, you would specify the routing profile as an access controlled resource, and then specify which tag _Key:value_ pair you would like to enable access to. +To use tags to control access to resources within the admin website of your Connect Customer instance, you need to configure the access control section within a given security profile. For example, to control access to a routing profile based on the tags you've assigned to it, you would specify the routing profile as an access controlled resource, and then specify which tag _Key:value_ pair you would like to enable access to. @@ -33 +33 @@ Users can be assigned a maximum of three security profiles that contain access c -Service linked roles are required in order to configure [resource tags](https://docs.aws.amazon.com/connect/latest/adminguide/tagging.html) or [access control tags](https://docs.aws.amazon.com/connect/latest/adminguide/tag-based-access-control.html). If your instance was created after October 2018, this will be available by default with your Amazon Connect instance. However if you have an older instance, refer to [Use service-linked roles for Amazon Connect](https://docs.aws.amazon.com/connect/latest/adminguide/connect-slr.html) for instructions for how to enable service linked roles. +Service linked roles are required in order to configure [resource tags](https://docs.aws.amazon.com/connect/latest/adminguide/tagging.html) or [access control tags](https://docs.aws.amazon.com/connect/latest/adminguide/tag-based-access-control.html). If your instance was created after October 2018, this will be available by default with your Connect Customer instance. However if you have an older instance, refer to [Use service-linked roles for Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/connect-slr.html) for instructions for how to enable service linked roles. @@ -37 +37 @@ Service linked roles are required in order to configure [resource tags](https:// -Applying tag-based access controls is an advanced configuration feature that is supported by Amazon Connect and that follows the AWS shared responsibility model. It is important to ensure that you are correctly configuring your instance to comply with your desired authorization needs. For more information, review the [AWS shared responsibilities model](https://aws.amazon.com/compliance/shared-responsibility-model/). +Applying tag-based access controls is an advanced configuration feature that is supported by Connect Customer and that follows the AWS shared responsibility model. It is important to ensure that you are correctly configuring your instance to comply with your desired authorization needs. For more information, review the [AWS shared responsibilities model](https://aws.amazon.com/compliance/shared-responsibility-model/). @@ -43 +43 @@ Tag-based access controls are enabled at the resource level, which means that ea -When logged in to the Amazon Connect console with tag-based access controls applied, users will not be able to access historical change logs for the resources that they are restricted on. +When logged in to the Connect Customer console with tag-based access controls applied, users will not be able to access historical change logs for the resources that they are restricted on. @@ -45 +45 @@ When logged in to the Amazon Connect console with tag-based access controls appl -As a best practice, you should disable access to the following resources/modules when applying tag-based access controls within the Amazon Connect console. If you do not disable access to these resources, users with tag-based access controls on a particular resource that view these pages may see an unrestricted list of users, security profiles, routing profiles, queues, flows, or flow modules. For more information on how to manage permissions, see [List of security profile permissions in Amazon Connect](./security-profile-list.html). +As a best practice, you should disable access to the following resources/modules when applying tag-based access controls within the Connect Customer console. If you do not disable access to these resources, users with tag-based access controls on a particular resource that view these pages may see an unrestricted list of users, security profiles, routing profiles, queues, flows, or flow modules. For more information on how to manage permissions, see [List of security profile permissions in Connect Customer](./security-profile-list.html). @@ -71 +71 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Update security profiles in Amazon Connect +Update security profiles in Connect Customer