AWS connect documentation change
Summary
Updated product name references from 'Amazon Connect' to 'Connect Customer' throughout the documentation. Added migration instructions for enhanced tag-based access controls with a January 15, 2026 deadline.
Security assessment
Changes are rebranding updates (Amazon Connect → Connect Customer) and migration instructions. No security vulnerabilities are mentioned or addressed. The documentation continues to explain existing tag-based access controls, which is a security feature, but doesn't add new security documentation.
Diff
diff --git a/connect/latest/adminguide/dashboard-tag-based-access-control.md b/connect/latest/adminguide/dashboard-tag-based-access-control.md index 8770acb0e..a260cef2e 100644 --- a//connect/latest/adminguide/dashboard-tag-based-access-control.md +++ b//connect/latest/adminguide/dashboard-tag-based-access-control.md @@ -9 +9 @@ How to enable tag-based access control for dashboards and reportsImportant thing -# Apply tag-based access controls to dashboards and reports in Amazon Connect +# Apply tag-based access controls to dashboards and reports in Connect Customer @@ -13 +13 @@ You can use resource tags and access control tags to apply granular access to us -Tag-based access controls enable you to configure granular access to specific resources based on assigned resource tags. You can configure tag-based access controls by using the API or the Amazon Connect admin website for supported resources. You must configure resource tags and access control tags before tag-based access control is applied to users, queues, routing profiles, flows, flow modules, evaluation forms, and test cases on analytics pages. For more information, see [Add tags to resources in Amazon Connect](./tagging.html) and [Apply tag-based access control in Amazon Connect](./tag-based-access-control.html). +Tag-based access controls enable you to configure granular access to specific resources based on assigned resource tags. You can configure tag-based access controls by using the API or the Connect Customer admin website for supported resources. You must configure resource tags and access control tags before tag-based access control is applied to users, queues, routing profiles, flows, flow modules, evaluation forms, and test cases on analytics pages. For more information, see [Add tags to resources in Connect Customer](./tagging.html) and [Apply tag-based access control in Connect Customer](./tag-based-access-control.html). @@ -30 +30 @@ To apply tags to control access to users, queues, routing profiles, flows, flow - * Apply tags to the resources that you're going to use in the dashboards and reports, such as users, queues, routing profiles, flows, flow modules, evaluation forms, and test cases. For more information, see [Add tags to resources in Amazon Connect](./tagging.html). + * Apply tags to the resources that you're going to use in the dashboards and reports, such as users, queues, routing profiles, flows, flow modules, evaluation forms, and test cases. For more information, see [Add tags to resources in Connect Customer](./tagging.html). @@ -61 +61 @@ OR -Additionally, you will need one or more relevant permissions to view specific resource data on dashboards and reports: **Routing profiles - View** , **Queues - View** , **Users - View** , **Test Cases - View** , **Evaluation forms \- manage form definitions - View** , **Flows - View** , **Flow modules - View** , and **Bot - View**. The following image shows an example of security profile permissions that grant users the ability to view routing profiles, queues, and Amazon Connect user accounts. +Additionally, you will need one or more relevant permissions to view specific resource data on dashboards and reports: **Routing profiles - View** , **Queues - View** , **Users - View** , **Test Cases - View** , **Evaluation forms \- manage form definitions - View** , **Flows - View** , **Flow modules - View** , and **Bot - View**. The following image shows an example of security profile permissions that grant users the ability to view routing profiles, queues, and Connect Customer user accounts. @@ -75 +75 @@ Additionally, you will need one or more relevant permissions to view specific re - * The tag-based access control experience on the **Real-time metrics** , **Historical metrics** and **Agent Activity Audit** page remains unchanged after this launch for users that had tag based access controls enabled in their security profile before January 15, 2026. It will continue to work the same way. However, if you would like the enhanced tag based access controls experience on your historical metrics, real-time metrics, and Agent Activity Audit report, please contact the Amazon Connect service team to assist with the migration. When you migrate to the new tag based access controls experience, please note that starting January 15, 2026, the historical metrics, and Agent Activity Audit report will display 2 months of historical data. The retention period will increase by 1 day each day. + * The tag-based access control experience on the **Real-time metrics** , **Historical metrics** and **Agent Activity Audit** page remains unchanged after this launch for users that had tag based access controls enabled in their security profile before January 15, 2026. It will continue to work the same way. However, if you would like the enhanced tag based access controls experience on your historical metrics, real-time metrics, and Agent Activity Audit report, please contact the Connect Customer service team to assist with the migration. When you migrate to the new tag based access controls experience, please note that starting January 15, 2026, the historical metrics, and Agent Activity Audit report will display 2 months of historical data. The retention period will increase by 1 day each day.