Required permissions for using custom IAM policies to manage Connect Customer Cases
If you're using custom IAM policies to manage access to the Connect Customer Cases, your users need some or all of the permissions listed in this article, depending on the tasks they need to do.
View Cases domain details
There are two options for granting users IAM permissions to view Cases domain details on the Connect Customer console.
Option 1: Minimum required IAM permissions
To view Cases domain details in the Connect Customer console, users must have the following IAM permissions:
-
connect:ListInstances -
ds:DescribeDirectories -
connect:ListIntegrationAssociations -
cases:GetDomain
Following is a sample IAM policy with these permissions:
Note the following:
-
cases:GetDomainAction is required on Resource* -
connect:ListIntegrationAssociationsaction supports theinstanceresource type. See the table in Actions defined by Connect Customer.
Option 2: Update the existing Connect Customer policy with cases:GetDomain and profile:SearchProfiles
Include the AmazonConnectReadOnlyAccess policy, and add
cases:GetDomain, as shown in the following example.
Onboard to Cases
There are two options for granting users IAM permissions to onboard to Cases using the Connect Customer console.
Option 1: Minimum required permissions
To onboard to Cases by using the Connect Customer console, users must have the following IAM permissions:
-
connect:ListInstances -
ds:DescribeDirectories -
connect:ListIntegrationAssociations -
cases:GetDomain -
cases:CreateDomain -
connect:CreateIntegrationAssociation -
connect:DescribeInstance -
iam:PutRolePolicy -
profile:SearchProfiles
Following is a sample IAM policy with these permissions:
Note the following:
-
cases:GetDomainAction is required on Resource* -
You can scope the permissions to specific Connect Customer tasks by using the information in Actions, resources, and condition keys for Connect Customer.
-
profile:SearchProfilesAction is required because theCreateCaseAPI calls theSearchProfilesAPI to search for customer profiles to validate against, and then associate the profile with the case.
Option 2: Use a combination of existing policies
The following combination of policies will also work:
-
AmazonConnect_FullAccess policy
-
iam:PutRolePolicyto modify the service-linked role. For an example, see AWS managed policy: AmazonConnect_FullAccess policy. -
The following IAM policy:
Enable Cases when you create an instance
To enable Cases on the Data storage step of instance creation, users need the permissions for creating an instance in Connect Customer console home page, plus the following permissions for the options they select.
| Option selected | Additional permissions |
|---|---|
| Enable Cases |
|
| Enable Cases event streams |
|
| Enable Cases event streams with Customer Profiles enabled |
|
Note the following:
-
cases:PutCaseEventConfigurationsets the event configuration to include all case fields. The user's policy must allow the action on the domain's field resource,arn:aws:cases:. If the policy allows only specific fields, the request fails with anregion:account-id:domain/domain-id/field/*AccessDeniedException. -
Scope
iam:PassRoletoarn:aws:iam::and add the conditionaccount-id:role/service-role/AmazonConnectCasesEventBridgeRole-*iam:PassedToService=events.amazonaws.com.
View and configure Cases integrations
To view integration status on the Cases page, users need the permissions in View Cases domain details, plus the following:
-
cases:GetCaseEventConfiguration -
events:DescribeRule -
events:DescribeEventBus -
app-integrations:GetEventIntegration -
profile:ListAccountIntegrations -
profile:ListIntegrations -
profile:GetIntegration
To choose Configure, users also need the permissions in Enable Cases when you create an instance for the integration that they
configure, except cases:CreateDomain.