AWS Entity Resolution vs Equifax Identity Matching

AWS Entity Resolution links records that may describe the same customer, product, business, or healthcare entity across applications, channels, and data stores. It offers rule-based, machine learning, and data service provider matching. Rule-based users can adjust input fields, priorities, and rules; the preconfigured machine learning model compares consumer fields such as names, email addresses, phone numbers, addresses, and birth dates, then assigns match groups confidence scores from 0.0 to 1.0. Inputs come from AWS Glue, with a limit of 20. Rule-based matching can process new Amazon S3 data incrementally, and the GetMatchId API can synchronously look up an existing match ID while hashing personally identifiable attributes. Access is through the AWS console and API. Personally identifiable data is encrypted at rest by default with AWS-owned keys, with customer-managed symmetric AWS KMS keys also supported. Provider matching includes LiveRamp, TransUnion, and Unified ID 2.0 identifiers, subject to a provider license agreement. AWS states that the service meets PCI DSS and SOC 1, SOC 2, and SOC 3 measures. Pricing is paid, from $0.10; there is no free plan.

Equifax Identity Matching links customer information held in disconnected sources, including records where names or addresses differ. It assigns persistent consumer identifiers and can create consumer, household, and address keys, helping organizations form a single customer view. Equifax says it compares multiple datasets and data-element combinations, and can combine company records with consumer credit and specialty finance data. Matching and updates are described as cloud-based and near real time, with incremental key changes available through delta services. Delivery options include batch services, an online API, and cloud-native Keying as a Service in Snowflake or Google Cloud Platform BigQuery environments. Confidential Keying keeps raw personal information in a customer cloud environment. Data is encrypted and tokenized, usage is regulated by GLBA, and processes are regularly validated. OAuth 2.0 client credentials secure APIs; production access requires credentials and whitelisted IP addresses. Pricing is on request.