Unable to create Amazon connect customer profile through APP Flow

To successfully create Amazon Connect Customer Profiles through Amazon AppFlow, there are several prerequisites and potential issues to check:

First, ensure you've met all the required prerequisites:

• You must have an Amazon Connect instance
• The Customer Profiles feature must be enabled for your Amazon Connect instance
• Customer Profiles must be configured to encrypt your data under a KMS key

Since your AppFlow execution shows success but no profiles are being created, here are some troubleshooting steps:

1. Verify that Customer Profiles is properly enabled for your Amazon Connect instance. This creates a customer profiles domain, which is the container for your customer data.

2. Check that you've properly set up the data mappings in Customer Profiles after creating the AppFlow flow. The AppFlow success only indicates that data was transferred, but the mappings in Amazon Connect define how that data is used to create profiles.

3. Ensure your CSV data contains valid values for the required fields. Customer Profiles has limitations, such as field values not exceeding 255 characters.

4. Look for any throttling issues with the Customer Profiles API, which could prevent profile creation even if the data transfer was successful.

5. Check if there are any availability issues with the Customer Profiles service.

Without specific error logs, it's difficult to pinpoint the exact failure point. You might want to check CloudWatch Logs for any related Amazon Connect or AppFlow logs that could provide more details about the issue.
Sources
Amazon Connect connector for Amazon AppFlow - Amazon AppFlow
Flow block in Amazon Connect: Customer profiles - Amazon Connect

The behavior you're seeing is almost always the object type mapping, not the AppFlow transfer. AppFlow reporting "success" just means the records were delivered to Customer Profiles. Whether a standard profile actually gets created is decided by the mapping, and there are three settings in it that produce exactly this "success but no profile" symptom.

1. AllowProfileCreation is the usual culprit. It defaults to FALSE, and when it's FALSE, Customer Profiles only tries to match each incoming record to an existing standard profile. If it finds no match, it stores the ingested object and does not create a new profile. Since you're loading fresh data with nothing to match against, everything ingests but no profiles appear. Set AllowProfileCreation to TRUE so it creates a profile when there's no existing match.

2. You need at least one key defined. Keys do double duty: during ingestion they're how Customer Profiles decides which profile an object belongs to, and afterward they're what SearchProfiles uses. Pick a unique identifier from your CSV (account number, email, customer ID) and define it as a key. Without one, profile assignment doesn't work cleanly.

3. Fields have to target the standard profile. In the field definitions, the only supported target object is _profile, so your CSV columns need Target values that map into the standard profile (name, email, account number, etc.). Fields with no target only exist to feed a key, they won't populate a profile on their own.

Also worth checking: if you created the flow straight from the AppFlow console, you may not have a proper object type mapping at all. The cleaner path is to set the S3 integration up from inside Customer Profiles, which creates the flow and the mapping together.

On the missing logs: look at AppFlow's run history first for records processed vs. filtered vs. failed, to confirm the rows actually left S3. Then, instead of hunting for a profile-creation log, verify with the APIs, ListProfileObjects will usually show the ingested objects even when no standard profile exists, and SearchProfiles using one of your defined key values confirms whether a profile was created. A frequent false alarm is that profiles were created but you're searching on a field that isn't a defined key, so they look missing when they aren't.

Order I'd work through it: set AllowProfileCreation to TRUE → confirm a unique key is defined → confirm columns target _profile → re-run → SearchProfiles on the key value to verify.