AWS entityresolution documentation change
Summary
Replaced 'Amazon Connect Customer Profiles' with 'Connect Customer Customer Profiles' throughout (likely typo).
Security assessment
Consistent branding/text change without security impact. No security features or vulnerabilities referenced.
Diff
diff --git a/entityresolution/latest/userguide/create-matching-workflow.md b/entityresolution/latest/userguide/create-matching-workflow.md index 25c19d43c..8beb75020 100644 --- a//entityresolution/latest/userguide/create-matching-workflow.md +++ b//entityresolution/latest/userguide/create-matching-workflow.md @@ -63 +63 @@ Provider service-based matching -Uses third-party data providers to enrich and validate your data before matching. This type of matching is not compatible with Amazon Connect Customer Profiles output. +Uses third-party data providers to enrich and validate your data before matching. This type of matching is not compatible with Connect Customer Customer Profiles output. @@ -71 +71 @@ AWS Entity Resolution can write data output files to: - * Amazon Connect Customer Profiles (for customer data deduplication) + * Connect Customer Customer Profiles (for customer data deduplication) @@ -78 +78 @@ AWS Entity Resolution can write data output files to: -Exporting to Amazon Connect Customer Profiles is not compatible with provider-based matching. To export to Amazon Connect Customer Profiles, you must use rule-based matching or machine learning-based matching. +Exporting to Connect Customer Customer Profiles is not compatible with provider-based matching. To export to Connect Customer Customer Profiles, you must use rule-based matching or machine learning-based matching. @@ -92 +92 @@ Matching type | S3 output | Customer Profiles Output -After you create and run a matching workflow, you can view the results in your specified S3 location or in Amazon Connect Customer Profiles. Matching workflows generate IDs after the data is indexed. +After you create and run a matching workflow, you can view the results in your specified S3 location or in Connect Customer Customer Profiles. Matching workflows generate IDs after the data is indexed. @@ -107 +107 @@ For each run for S3 output destinations: -For each run for Amazon Connect Customer Profiles output destinations: +For each run for Connect Customer Customer Profiles output destinations: @@ -109 +109 @@ For each run for Amazon Connect Customer Profiles output destinations: - * Deduplicated customer records are sent directly to your Amazon Connect instance + * Deduplicated customer records are sent directly to your Connect Customer instance @@ -113 +113 @@ For each run for Amazon Connect Customer Profiles output destinations: - * Existing profiles in Amazon Connect are not included in the deduplication process + * Existing profiles in Connect Customer are not included in the deduplication process