Amazon Route 53 endpoints and quotas
The following are the service endpoints and service quotas for this service. To connect programmatically to an AWS service, you use an endpoint. In addition to the standard AWS endpoints, some AWS services offer FIPS endpoints in selected Regions. For more information, see AWS service endpoints. 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.
Service endpoints
Hosted zones, records, health checks, DNS query logs, reusable delegation sets, traffic policies, and cost allocation tags
When you use the AWS CLI or SDKs to submit requests, you can either leave the Region and endpoint unspecified, or specify the applicable Region:
Route 53 in AWS Regions other than the Beijing and Ningxia Regions: specify us-east-1 as the Region.
Route 53 in the Beijing and Ningxia Regions: specify cn-northwest-1.
When you use the Route 53 API to submit requests, use the same Regions as above to sign requests.
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 | route53.amazonaws.com | HTTPS |
| US East (N. Virginia) | us-east-1 | route53.amazonaws.com | HTTPS |
| US West (N. California) | us-west-1 | route53.amazonaws.com | HTTPS |
| US West (Oregon) | us-west-2 | route53.amazonaws.com | HTTPS |
| Africa (Cape Town) | af-south-1 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Hong Kong) | ap-east-1 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Hyderabad) | ap-south-2 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Jakarta) | ap-southeast-3 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Malaysia) | ap-southeast-5 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Melbourne) | ap-southeast-4 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Osaka) | ap-northeast-3 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | route53.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | route53.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 | route53.amazonaws.com | HTTPS |
| Canada West (Calgary) | ca-west-1 | route53.amazonaws.com | HTTPS |
| Europe (Frankfurt) | eu-central-1 | route53.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | route53.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | route53.amazonaws.com | HTTPS |
| Europe (Milan) | eu-south-1 | route53.amazonaws.com | HTTPS |
| Europe (Paris) | eu-west-3 | route53.amazonaws.com | HTTPS |
| Europe (Spain) | eu-south-2 | route53.amazonaws.com | HTTPS |
| Europe (Stockholm) | eu-north-1 | route53.amazonaws.com | HTTPS |
| Europe (Zurich) | eu-central-2 | route53.amazonaws.com | HTTPS |
| Israel (Tel Aviv) | il-central-1 | route53.amazonaws.com | HTTPS |
| Middle East (Bahrain) | me-south-1 | route53.amazonaws.com | HTTPS |
| Middle East (UAE) | me-central-1 | route53.amazonaws.com | HTTPS |
| South America (São Paulo) | sa-east-1 | route53.amazonaws.com | HTTPS |
Requests for domain registration
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (N. Virginia) | us-east-1 | route53domains.us-east-1.amazonaws.com | HTTPS |
Requests for Route 53 Resolver
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 | route53resolver.us-east-2.amazonaws.com | HTTPS |
| US East (N. Virginia) | us-east-1 | route53resolver.us-east-1.amazonaws.com | HTTPS |
| US West (N. California) | us-west-1 | route53resolver.us-west-1.amazonaws.com | HTTPS |
| US West (Oregon) | us-west-2 | route53resolver.us-west-2.amazonaws.com | HTTPS |
| Africa (Cape Town) | af-south-1 | route53resolver.af-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Hong Kong) | ap-east-1 | route53resolver.ap-east-1.amazonaws.com | HTTPS |
| Asia Pacific (Hyderabad) | ap-south-2 | route53resolver.ap-south-2.amazonaws.com | HTTPS |
| Asia Pacific (Jakarta) | ap-southeast-3 | route53resolver.ap-southeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Malaysia) | ap-southeast-5 | route53resolver.ap-southeast-5.amazonaws.com | HTTPS |
| Asia Pacific (Melbourne) | ap-southeast-4 | route53resolver.ap-southeast-4.amazonaws.com | HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | route53resolver.ap-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Osaka) | ap-northeast-3 | route53resolver.ap-northeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | route53resolver.ap-northeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | route53resolver.ap-southeast-1.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | route53resolver.ap-southeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | route53resolver.ap-northeast-1.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 | route53resolver.ca-central-1.amazonaws.com | HTTPS |
| Canada West (Calgary) | ca-west-1 | route53resolver.ca-west-1.amazonaws.com | HTTPS |
| Europe (Frankfurt) | eu-central-1 | route53resolver.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | route53resolver.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | route53resolver.eu-west-2.amazonaws.com | HTTPS |
| Europe (Milan) | eu-south-1 | route53resolver.eu-south-1.amazonaws.com | HTTPS |
| Europe (Paris) | eu-west-3 | route53resolver.eu-west-3.amazonaws.com | HTTPS |
| Europe (Spain) | eu-south-2 | route53resolver.eu-south-2.amazonaws.com | HTTPS |
| Europe (Stockholm) | eu-north-1 | route53resolver.eu-north-1.amazonaws.com | HTTPS |
| Europe (Zurich) | eu-central-2 | route53resolver.eu-central-2.amazonaws.com | HTTPS |
| Israel (Tel Aviv) | il-central-1 | route53resolver.il-central-1.amazonaws.com | HTTPS |
| Middle East (Bahrain) | me-south-1 | route53resolver.me-south-1.amazonaws.com | HTTPS |
| Middle East (UAE) | me-central-1 | route53resolver.me-central-1.amazonaws.com | HTTPS |
| South America (São Paulo) | sa-east-1 | route53resolver.sa-east-1.amazonaws.com | HTTPS |
| AWS GovCloud (US-East) | us-gov-east-1 | route53resolver.us-gov-east-1.amazonaws.com | HTTPS |
| AWS GovCloud (US-West) | us-gov-west-1 | route53resolver.us-gov-west-1.amazonaws.com | HTTPS |
Requests for Route 53 Profiles
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 | route53profiles.us-east-2.amazonaws.com | HTTPS |
| US East (N. Virginia) | us-east-1 | route53profiles.us-east-1.amazonaws.com | HTTPS |
| US West (N. California) | us-west-1 | route53profiles.us-west-1.amazonaws.com | HTTPS |
| US West (Oregon) | us-west-2 | route53profiles.us-west-2.amazonaws.com | HTTPS |
| Africa (Cape Town) | af-south-1 | route53profiles.af-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Hong Kong) | ap-east-1 | route53profiles.ap-east-1.amazonaws.com | HTTPS |
| Asia Pacific (Hyderabad) | ap-south-2 | route53profiles.ap-south-2.amazonaws.com | HTTPS |
| Asia Pacific (Jakarta) | ap-southeast-3 | route53profiles.ap-southeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Melbourne) | ap-southeast-4 | route53profiles.ap-southeast-4.amazonaws.com | HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | route53profiles.ap-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Osaka) | ap-northeast-3 | route53profiles.ap-northeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | route53profiles.ap-northeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | route53profiles.ap-southeast-1.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | route53profiles.ap-southeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | route53profiles.ap-northeast-1.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 | route53profiles.ca-central-1.amazonaws.com | HTTPS |
| Canada West (Calgary) | ca-west-1 | route53profiles.ca-west-1.amazonaws.com | HTTPS |
| Europe (Frankfurt) | eu-central-1 | route53profiles.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | route53profiles.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | route53profiles.eu-west-2.amazonaws.com | HTTPS |
| Europe (Milan) | eu-south-1 | route53profiles.eu-south-1.amazonaws.com | HTTPS |
| Europe (Paris) | eu-west-3 | route53profiles.eu-west-3.amazonaws.com | HTTPS |
| Europe (Spain) | eu-south-2 | route53profiles.eu-south-2.amazonaws.com | HTTPS |
| Europe (Stockholm) | eu-north-1 | route53profiles.eu-north-1.amazonaws.com | HTTPS |
| Europe (Zurich) | eu-central-2 | route53profiles.eu-central-2.amazonaws.com | HTTPS |
| Israel (Tel Aviv) | il-central-1 | route53profiles.il-central-1.amazonaws.com | HTTPS |
| Middle East (Bahrain) | me-south-1 | route53profiles.me-south-1.amazonaws.com | HTTPS |
| Middle East (UAE) | me-central-1 | route53profiles.me-central-1.amazonaws.com | HTTPS |
| South America (São Paulo) | sa-east-1 | route53profiles.sa-east-1.amazonaws.com | HTTPS |
| AWS GovCloud (US-East) | us-gov-east-1 | route53profiles.us-gov-east-1.amazonaws.com | HTTPS |
| AWS GovCloud (US-West) | us-gov-west-1 | route53profiles.us-gov-west-1.amazonaws.com | HTTPS |
Requests for Route 53 auto naming
Amazon Route 53 auto naming has been released as a separate service, AWS Cloud Map. For a list of service endpoints, see Service endpoints. For AWS Cloud Map documentation, see AWS Cloud Map Documentation.
Service quotas
The following are the service quotas for Route 53
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Amazon VPCs that you can associate with a private hosted zone | Each supported Region: 300 |
Yes |
The maximum number of Amazon VPCs that you can associate with a private hosted zone |
| CIDR blocks per collection | Each supported Region: 1,000 |
Yes |
The maximum number of CIDR blocks that you can create per CIDR collection |
| CIDR collections | Each supported Region: 5 |
Yes |
The maximum number of CIDR collections that you can create per account |
| Child health checks that a calculated health check can monitor | Each supported Region: 255 | No | The maximum number of child health checks that a calculated health check can monitor |
| Domain count limit | Each supported Region: 20 |
Yes |
The maximum number of domains you can register using this account |
| Health checks | Each supported Region: 200 |
Yes |
The maximum number of health checks that you can create using this account |
| Hosted zones | Each supported Region: 500 |
Yes |
The maximum number of hosted zones that you can create using this account |
| Hosted zones that can use the same reusable delegation set | Each supported Region: 100 |
Yes |
The maximum number of hosted zones that can use the same reusable delegation set |
| Records per hosted zone | Each supported Region: 10,000 |
Yes |
The maximum number of records that you can create in a hosted zone |
| Reusable delegation sets | Each supported Region: 100 |
Yes |
The maximum number of reusable delegation sets that you can create using this account |
| Traffic flow policies | Each supported Region: 50 |
Yes |
The maximum number of traffic flow policies that you can create using this account |
| Traffic flow policy records | Each supported Region: 5 |
Yes |
The maximum number of traffic flow policy records that you can create using this account |
The following quotas are for Route 53 Resolver.
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Associations between resolver rules and VPCs per AWS Region | Each supported Region: 2,000 |
Yes |
Maximum number of associations between resolver rules and VPCs per AWS Region |
| DNS Firewall rule group associations per VPC | Each supported Region: 5 | No | The maximum number of DNS Firewall rule groups that you can associate to a VPC. |
| DNS Firewall rule groups associations to a Route 53 Profile. | Each supported Region: 5 | No | The maximum number of DNS Firewall rule groups that can be associated to a Route 53 Profile. |
| DNS Firewall rules groups per Region | Each supported Region: 1,000 |
Yes |
The maximum number of DNS Firewall rules groups per Region. |
| Domain lists per account | Each supported Region: 1,000 |
Yes |
The maximum number of domain lists for an account. |
| Domains in a file imported from S3 | Each supported Region: 250,000 |
Yes |
The maximum number of domains that you can import from a single file thats stored in an Amazon S3 bucket. |
| Domains per account | Each supported Region: 100,000 |
Yes |
The maximum number of domains that you can specify across all of the domain lists for an account. |
| IP addresses per resolver endpoint | Each supported Region: 6 |
Yes |
Maximum number of IP addresses per resolver endpoint |
| Maximum number of resolver endpoints per AWS Region | Each supported Region: 4 |
Yes |
Resolver endpoints per AWS Region |
| Resolver rule associations to a Route 53 Profile. | Each supported Region: 1,000 |
Yes |
The maximum number of Resolver rule associations per Route 53 Profile. |
| Resolver rules per AWS Region | Each supported Region: 1,000 |
Yes |
Maximum number of resolver rules per AWS Region |
| Rules in a DNS Firewall rule group | Each supported Region: 100 |
Yes |
The maximum number of rules in a DNS Firewall rule group. |
| Target IP addresses per resolver rule | Each supported Region: 6 | No | Maximum number of target IP addresses per resolver rule |
The following quotas are for Route 53 Profiles
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Private hosted zone associations to a Route 53 Profile. | Each supported Region: 1,000 |
Yes |
The maximum number of private hosted zones that can be associated to a Route 53 Profile. |
| Route 53 Profiles per account per Region. | Each supported Region: 5 |
Yes |
The maximum number of Route 53 Profiles per AWS account per Region. |
| VPC to Route 53 Profile associations per Region | Each supported Region: 1,000 |
Yes |
The maximum number of VPCs that can be associated to a Route 53 Profile. |
For more information, see Route 53 quotas in the Amazon Route 53 Developer Guide.
