Set up integration for featured applications in Amazon Connect - Amazon Connect

Set up integration for featured applications in Amazon Connect

These integrations use Amazon Connect featured applications to provide periodic updates to Amazon Connect Customer Profiles.

Before you begin

Bulk ingestion of data

When you set up your integration, you are prompted to enter a date how far back you want to go to ingest data. If you choose a date that is more than two months ago, Customer Profiles automatically enables bulk ingestion by creating multiple flows. It does this so you don't have to calculate how many flows you need to ingest data.

When automatic bulk ingestion is enabled, Customer Profiles does the following:

  • Sets the batch size to two months.

  • Retries on transient failures up to three times before failing.

You can use the CreateIntegrationWorkflowRequest API to call your own batch size.

Why am I asked to select or create an IAM role?

For Salesforce, Marketo, and ServiceNow, Customer Profiles helps improve the historical ingestion of these sources by using your IAM role to create several workflows to ingest your data quickly and efficiently.

For these sources, if you select more than 60 days back in the Date for importing records date picker, you will be prompted to create a new IAM role or select an existing one. This role allows Customer Profiles to manage your integration. It provides Customer Profiles with the necessary permissions to update and create a workflow to ingest your data. After the workflow is complete, Customer Profiles creates a standard, continuous integration that ingests your new data as it is updated in your source.

The role created in the console is only useable by the domain it was created on. This is because Amazon Connect limits the access of the role to only the KMS key used by the domain.

For more information, see Grant least privilege access to your Customer Profiles execution role.

Grant least privilege access to your Customer Profiles execution role

If you want to create your own IAM role, we recommend using the permissions shown in the following code to limit the role to the least permissions needed. Use the snippet below to create your role manually. Use your own KMS key and specify your Region where needed.

{ "Version": "2012-10-17", "Statement": [ { "Condition": { "ForAnyValue:StringEquals": { "aws:RequestTag/awsOwningService": "customer-profiles-integration-workflow" } }, "Action": [ "appflow:CreateFlow", "appflow:TagResource", "profile:TagResource", "profile:PutIntegration" ], "Resource": "*", "Effect": "Allow", "Sid": "CreateFlowResources" }, { "Action": [ "appflow:UseConnectorProfile" ], "Resource": "*", "Effect": "Allow", "Sid": "UseConnectorResources" }, { "Condition": { "ForAnyValue:StringEquals": { "aws:ResourceTag/awsOwningService": "customer-profiles-integration-workflow" } }, "Action": [ "appflow:DescribeFlow", "appflow:DescribeFlowExecutionRecords", "appflow:DeleteFlow", "appflow:StartFlow", "appflow:StopFlow", "appflow:UpdateFlow", "profile:DeleteIntegration" ], "Resource": "*", "Effect": "Allow", "Sid": "AccessFlowResources" }, { "Action": [ "kms:CreateGrant", "kms:ListGrants" ], "Resource": "{{YourKMSKeyConsumedByTheDomain}}", "Condition": { "StringEquals": { "kms:ViaService": [ "appflow.{{region}}" ] } }, "Effect": "Allow", "Sid": "KMSAppflow" }, { "Action": [ "kms:CreateGrant" ], "Resource": "{{YourKMSKeyConsumedByTheDomain}}", "Condition": { "StringEquals": { "kms:ViaService": [ "profile.{{region}}" ] }, "ForAllValues:StringEquals": { "kms:GrantOperations": [ "Decrypt" ] } }, "Effect": "Allow", "Sid": "KMSCustomerProfiles" } ] }

Monitor your Customer Profiles integrations

After your connection is established, if it stops working, delete the integration and then re-establish it.

What to do if objects aren't being sent

If an object fails to be sent, choose Flow details to learn more about what's gone wrong.

You may need to delete the configuration and re-connect to the external application.