AWS connect documentation change
Summary
Increased maximum displayed resources in real-time metrics tables from 100 to 500 across multiple sections
Security assessment
The changes update operational capacity limits (100 to 500 resources) in tag-based access control documentation. While tag-based access control is a security feature, this specific change relates to scalability/performance improvements rather than addressing vulnerabilities or enhancing security controls. No security weaknesses or incidents are mentioned.
Diff
diff --git a/connect/latest/adminguide/rtm-tag-based-access-control.md b/connect/latest/adminguide/rtm-tag-based-access-control.md index c95b86cf8..e5f0cfeb2 100644 --- a//connect/latest/adminguide/rtm-tag-based-access-control.md +++ b//connect/latest/adminguide/rtm-tag-based-access-control.md @@ -32 +32 @@ You can configure tag-based access controls by using the Amazon Connect admin we - * Amazon Connect can display up to 100 resources at a time on a real-time metrics table. For example, in an Agents table it can display up to 100 agents at a time. In a Queues table it can display up to 100 queues, and so on. + * Amazon Connect can display up to 500 resources at a time on a real-time metrics table. For example, in an Agents table it can display up to 500 agents at a time. In a Queues table it can display up to 500 queues, and so on. @@ -34 +34 @@ You can configure tag-based access controls by using the Amazon Connect admin we - * Very often fewer than 100 agents will appear on a real-time metrics table at any given time when tagging is enabled. Here's why: + * Very often fewer than 500 agents will appear on a real-time metrics table at any given time when tagging is enabled. Here's why: @@ -36 +36 @@ You can configure tag-based access controls by using the Amazon Connect admin we - * Amazon Connect can return a maximum of 100 agents at a time. + * Amazon Connect can return a maximum of 500 agents at a time. @@ -38 +38 @@ You can configure tag-based access controls by using the Amazon Connect admin we - * When tagging is enabled, Amazon Connect selects the first 100 agents who have the appropriate tags, and then displays only those agents in that group of 100 **who are active** (Online or On Contact). Because not all of the 100 tagged agents may be active, it is very likely fewer than 100 tagged agents will be displayed in the table. + * When tagging is enabled, Amazon Connect selects the first 500 agents who have the appropriate tags, and then displays only those agents in that group of 500 **who are active** (Online or On Contact). Because not all of the 500 tagged agents may be active, it is very likely fewer than 500 tagged agents will be displayed in the table. @@ -40 +40 @@ You can configure tag-based access controls by using the Amazon Connect admin we - * For example, you have 200 tagged agents. In the first group of 100 tagged agents only 50 are online. Amazon Connect selects the first 100 tagged agents but displays only 50 because they are currently active. It does not select the first 100 active agents. + * For example, you have 1000 tagged agents. In the first group of 500 tagged agents only 50 are online. Amazon Connect selects the first 500 tagged agents but displays only 50 because they are currently active. It does not select the first 500 active agents. @@ -74 +74 @@ You must configure user resource tags and access control tags before tag-based a -Amazon Connect displays up to 100 resources at a time on the real-time metrics report. For agents in particular when tags are applied it's very likely that fewer than 100 agents will be displayed. We recommend the following workaround to view the status of hundreds of agents, queues, and routing profiles when tags are applied. +Amazon Connect displays up to 500 resources at a time on the real-time metrics report. For agents in particular when tags are applied it's very likely that fewer than 500 agents will be displayed. We recommend the following workaround to view the status of hundreds of agents, queues, and routing profiles when tags are applied. @@ -76 +76 @@ Amazon Connect displays up to 100 resources at a time on the real-time metrics r - 1. Add one table for each group of 100 resources. For example, you have 500 agents. You would create 5 Agent tables. + 1. Add one table for each group of 500 resources. For example, you have 2500 agents. You would create 5 Agent tables. @@ -78 +78 @@ Amazon Connect displays up to 100 resources at a time on the real-time metrics r - 2. For each table, manually filter to add up to 100 resources. For example, to add agents to the first table, you would choose to filter by **Agents** , and then choose 100 agents to include in the table, as shown in the following image. In table 2, add the next group of 100 agents, and so on. + 2. For each table, manually filter to add up to 500 resources. For example, to add agents to the first table, you would choose to filter by **Agents** , and then choose 500 agents to include in the table, as shown in the following image. In table 2, add the next group of 500 agents, and so on. @@ -82 +82 @@ Amazon Connect displays up to 100 resources at a time on the real-time metrics r - 3. You will be able to view the data for all 500 resources across the 5 tables. When tags are applied to agents, each table will likely display fewer than 100 agents because not all of them may be active at the same time. + 3. You will be able to view the data for all 2500 resources across the 5 tables. When tags are applied to agents, each table will likely display fewer than 500 agents because not all of them may be active at the same time.