AWS Entity Resolution endpoints and quotas - AWS General Reference
Service endpointsService quotas

AWS Entity Resolution endpoints and quotas

This section lists the the service endpoints and service quotas for the service. To connect programmatically to an AWS service, you use an endpoint. For more information, see AWS service endpoints.

In addition to the standard AWS endpoints, some AWS services offer the following endpoints in some or all of the AWS Regions that the service is supported in:

  • IPv4 endpoints — These endpoints support only IPv4 requests and have the following format: service-name.region.amazonaws.com

  • Dual-stack endpoints — These endpoints support both IPv4 requests and IPv6 requests and have the following format: service-name.region.api.aws

  • FIPS endpoints — These endpoints comply with the Federal Information Processing Standards (FIPS) and can support either IPv4 requests or dual-stack (IPv4 and IPv6) requests. FIPS endpoints have the following format: service-name-fips.region.ip-endpoint-type, where ip-endpoint-type is amazonaws.com (for IPv4 requests) or api.aws (for IPv4 or IPv6 requests).

Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. For more information, see AWS service quotas.

Note

AWS recommends that you use Regional STS endpoints within your applications, and avoid using global (legacy) STS endpoints. Regional STS endpoints reduce latency, build in redundancy, and increase session token validity. For more information about configuring your applications to use a Regional STS endpoint, see AWS STS Regionalized endpoints in the AWS SDKs and Tools Reference Guide. For more information about global (legacy) AWS STS endpoints, including how to monitor for use of this type of endpoint, see How to use Regional AWS STS endpoints in the AWS Security blog.

Service endpoints

Region Name Region Endpoint Protocol
US East (Ohio) us-east-2

entityresolution.us-east-2.amazonaws.com

entityresolution-fips.us-east-2.amazonaws.com

HTTPS

HTTPS
US East (N. Virginia) us-east-1

entityresolution.us-east-1.amazonaws.com

entityresolution-fips.us-east-1.amazonaws.com

HTTPS

HTTPS
US West (Oregon) us-west-2

entityresolution.us-west-2.amazonaws.com

entityresolution-fips.us-west-2.amazonaws.com

HTTPS

HTTPS
Asia Pacific (Seoul) ap-northeast-2 entityresolution.ap-northeast-2.amazonaws.com HTTPS
Asia Pacific (Singapore) ap-southeast-1 entityresolution.ap-southeast-1.amazonaws.com HTTPS
Asia Pacific (Sydney) ap-southeast-2 entityresolution.ap-southeast-2.amazonaws.com HTTPS
Asia Pacific (Tokyo) ap-northeast-1 entityresolution.ap-northeast-1.amazonaws.com HTTPS
Europe (Frankfurt) eu-central-1 entityresolution.eu-central-1.amazonaws.com HTTPS
Europe (Ireland) eu-west-1 entityresolution.eu-west-1.amazonaws.com HTTPS
Europe (London) eu-west-2 entityresolution.eu-west-2.amazonaws.com HTTPS

Service quotas

Name Default Adjustable Description
Concurrent matching jobs 1 No The maximum number of concurrent matching jobs that can be run.
Data input 20 No This is the list of input tables that you want to use in a matching workflow. Each input corresponds to a column in your AWS Glue input data table, which contains the column name and additional information that AWS Entity Resolution uses for matching purposes. Inputs must contain Primary Key plus at least one additional input field.
Data output 750 No This is a list of OutputAttribute objects, each of which have the fields Name and Hashed. Each of these objects represent a column to be included in the AWS Glue output table and whether you want the values in the column to be hashed.
Data schema 25 No The maximum number of data schema input fields.
Match rule 15 No For rule-based matching, this is the rule number applied that generated a matched record set. This is part of Matching Workflow Metadata that will be included in output.
Matching Workflows 10 Yes The maximum number of matching workflows.
Number of rules per workflow 15 No The maximum number of rules per matching workflow.
Rate of GetMatchId API Requests 50 Yes The maximum number of GetCustomerID API requests per second.
Schema Mappings 50 Yes The maximum number of Schema Mappings that you can create in this account in the current AWS Region.
Unique match keys per across ruleset 15 No The maximum number of unique match keys per rule set. A match key instructs AWS Entity Resolution which input fields are to be considered as similar data and which are to be considered as different data. This helps AWS Entity Resolution automatically configure rule-based matching rules and compare similar data stored in different input fields.

For more information, see AWS Entity Resolution quotas in the AWS Entity Resolution User Guide.