AWS Security ChangesHomeSearch

AWS connect: Add per-resource permissions table and tag-based access notes for rules

Service: connect · 2026-11-10 · Documentation medium

File: connect/latest/adminguide/permissions-for-rules.md · Type: iam

Summary

Rewrites the rules permissions page: clarifies that creating/editing/deleting generative AI rules requires the Analytics and Optimization: Rules - Generative AI permission while viewing only needs Rules - View, and adds a new 'Permissions for resources in rules' section with a table mapping each rule resource (queues, agents, hierarchies, routing profiles, flows, AI agents, evaluation forms, etc.) to the required View permission, plus a note that tag-based or hierarchy-based access control limits which resources can be added to rules.

Security assessment

The change documents least-privilege IAM requirements for rule creation/editing and explicitly ties resource selection to View permissions and tag/hierarchy-based access control, which is authorization guidance rather than a fix for a specific vulnerability.

Evidence

+To add a resource to a rule condition or action, you need permission to view that resource. The following table lists the resources that you can use in rules, and the permission that you need for each.

Diff

diff --git a/connect/latest/adminguide/permissions-for-rules.md b/connect/latest/adminguide/permissions-for-rules.md
index 48cdead..0b5af9e 100644
--- a//connect/latest/adminguide/permissions-for-rules.md
+++ b//connect/latest/adminguide/permissions-for-rules.md
@@ -6,0 +7,2 @@
+Permissions for resources in rules
+
@@ -11 +13 @@ To view, edit, or add rules for automatic categorization, you must be assigned t
-To view, edit, or add rule that use generative AI (using the **Natural language - semantic match** condition), your security profile must additionally be assigned the **Analytics and Optimization: Rules - Generative AI** permission.
+To create, edit, or delete rules that use generative AI (using the **Natural language - semantic match** condition), your security profile must also have the **Analytics and Optimization: Rules \- Generative AI** permission. To view these rules, the **Rules - View** permission is enough.
@@ -13 +15 @@ To view, edit, or add rule that use generative AI (using the **Natural language
-To see agent names so you can add them to rules, you need **Users and permissions: Users - View** permissions in your security profile. 
+For more information, see [Assign permissions to use conversational analytics in Connect Customer](./permissions-for-contact-lens.html).
@@ -15 +17 @@ To see agent names so you can add them to rules, you need **Users and permission
-To see the queue names so you can add them to rules, you need **Routing: Queues - View** permissions in your security profile. 
+## Permissions for resources in rules
@@ -17 +19,15 @@ To see the queue names so you can add them to rules, you need **Routing: Queues
-For more information, see [Assign permissions to use conversational analytics in Connect Customer](./permissions-for-contact-lens.html).
+To add a resource to a rule condition or action, you need permission to view that resource. The following table lists the resources that you can use in rules, and the permission that you need for each.
+
+Resource | Permission | Where you use it in rules  
+---|---|---  
+Queues | **Routing: Queues - View** | Queue conditions, and queue filters in metric conditions  
+Agents | **Users and permissions: Users - View** | Agent conditions, agent filters in metric conditions, and notification recipients and exclusions  
+Agent hierarchies | **Users and permissions: Agent hierarchy - View** | Agent hierarchy conditions, and agent hierarchy filters in metric conditions  
+Routing profiles | **Routing: Routing profiles - View** | Routing profile conditions, and routing profile filters in metric conditions  
+Flows | **Channels and flows: Flows - View** | Flow filters in conditions, and the flow in a **Create Task** action  
+Flow modules | **Channels and flows: Flow modules - View** | Flow module filters in metric conditions  
+AI agents | **AI agents - View** | AI agent conditions, and AI agent filters in metric conditions  
+Evaluation forms | **Analytics and Optimization: Evaluation forms - manage form definitions - View** | Evaluation form conditions, and the form in a **Submit automated evaluation** action  
+Information extraction definitions | **Analytics and Optimization: Information extraction - definitions - View** | The definitions in an information extraction action  
+  
+Your security profile might use tag-based or hierarchy-based access control on a resource. If so, you can add only the resources that you have access to. For more information, see [Granular access controls on rules](./rules-tag-based-access-control.html).
@@ -27 +43 @@ Enter a script in a rule
-About contact attributes in a rule
+Granular access controls on rules