Big route53 accounts may cause dnsprovider to hit rate limits #39674

justinsb opened this Issue Jan 10, 2017 · 3 comments


None yet

2 participants


The route53 dnsprovider doesn't implement filtering. On Route53, there is a 5 request per second rate limit (per AWS account):

With pagination, it is very likely that we will issue more than 5 requests per second just listing resource records for a big zone.

We need to implement filtering.


@justinsb can you provide more details on the code base this is coming from?

@justinsb justinsb added the area/dns label Jan 12, 2017
@justinsb justinsb added a commit to justinsb/kubernetes that referenced this issue Jan 12, 2017
@justinsb justinsb dnsprovider: Support RRSet filtering by name/type
We add filtering by name & type, because providers can often push-down
the predicate, and thereby avoid more expensive calls.

On AWS in particular, this avoids paginating through multiple pages of
resource record sets (the API rate limits are based on rate of calls,
not on their complexity).

Issue #39674
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment