You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.
Mate version 0.6.1 ( and prior versions) causes a lot of traffic while it polls route53. My AWS account has 53 hosted zones and in those zones there are 10's of records in them. Mate, even with filtering enabled, still queries these zones and causes route53 query outages while looking at the route53 console.
I have not yet dug into the code, but I'm wondering if it is possible to set the query period and to set mate up to only query / control a certain zone. Basically I need to massively reduce the amount of DNS traffic that mate does.
I will also mention that I have a specific IAM role setup for mate that gives him ChangeResourceRecordSets in two hosted zones, he is also allowed to getchange. He also has unlimited access to elasticloadbalancing...
Mate version 0.6.1 ( and prior versions) causes a lot of traffic while it polls route53. My AWS account has 53 hosted zones and in those zones there are 10's of records in them. Mate, even with filtering enabled, still queries these zones and causes route53 query outages while looking at the route53 console.
I have not yet dug into the code, but I'm wondering if it is possible to set the query period and to set mate up to only query / control a certain zone. Basically I need to massively reduce the amount of DNS traffic that mate does.
I will also mention that I have a specific IAM role setup for mate that gives him ChangeResourceRecordSets in two hosted zones, he is also allowed to getchange. He also has unlimited access to elasticloadbalancing...
Some logs to checkout :
Gitst Of log
Some suggested behavior:
Thoughts?
The text was updated successfully, but these errors were encountered: