AWS Entity Resolution vs Lexer Identity Resolution

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.

Lexer Identity Resolution has no write-up on Specifiction yet; its figures are above.