AWS Documentation » Amazon Route 53 » Developer Guide » What Is Route 53 and How Does it Work? » Limits on Route 53 API Requests and Entity Counts	« Previous Next »
	Did this page help you? Yes \| No \| Tell us about it...

Limits on Route 53 API Requests and Entity Counts

Route 53 API requests are subject to the following limitations.

Request Limitation

Request	Limitation
`ChangeResourceRecordSets` requests	A request cannot contain more than 100 `Change` elements. A request cannot contain more than 1000 `ResourceRecord` elements. The sum of the number of characters (including spaces) in all `Value` elements in a request cannot exceed 32,000 characters.
Route 53 API requests	All requests: Five requests per second per AWS account. If you submit more than five requests per second, Route 53 returns an HTTP 400 error (`Bad request`). The response header also includes a `Code` element with a value of `Throttling` and a `Message` element with a value of `Rate exceeded`. ChangeResourceRecordSets requests: If Route 53 can't process a request before the next request arrives, it will reject subsequent requests for the same hosted zone and return an HTTP 400 error (`Bad request`). The response header also includes a `Code` element with a value of `PriorRequestNotComplete` and a `Message` element with a value of `The request was rejected because Route 53 was still processing a prior request.`

ChangeResourceRecordSets requests

A request cannot contain more than 100 Change elements.
A request cannot contain more than 1000 ResourceRecord elements.
The sum of the number of characters (including spaces) in all Value elements in a request cannot exceed 32,000 characters.

Route 53 API requests

All requests: Five requests per second per AWS account. If you submit more than five requests per second, Route 53 returns an HTTP 400 error (Bad request). The response header also includes a Code element with a value of Throttling and a Message element with a value of Rate exceeded.
ChangeResourceRecordSets requests: If Route 53 can't process a request before the next request arrives, it will reject subsequent requests for the same hosted zone and return an HTTP 400 error (Bad request). The response header also includes a Code element with a value of PriorRequestNotComplete and a Message element with a value of The request was rejected because Route 53 was still processing a prior request.

Route 53 entities are subject to the following limitations.

Entity	Limitation
Hosted zones	100 per AWS account. You can request a higher limit at http://aws.amazon.com/route53-request/.
Resource record sets	10,000 per hosted zone. You can request a higher limit at http://aws.amazon.com/route53-request/.
Weighted resource record sets	100 resource record sets that have the same name and type.
Resource records	100 per resource record set.
Health checks	50 active health checks per AWS account. You can request a higher limit at http://aws.amazon.com/route53-request/.

Document Conventions	« Previous Next »
Terms of Use	Did this page help you? Yes \| No \| Tell us about it...