So AWS has the concept of traffic flow diagrams that have different types of routing / health checks and multiple other features that could be factored out based on a zone similar to a template.
The thing is that in our case the template could contain the tree that would ultimately be formed and then it could simply be linked to all zones linked to that policy.
This will aid in altering zones in bulk or limit the amount of requests needed for such an operation.
BUT there is a catch each such zone has to have a policy record created with a specific version linking it to the correct flow. This link costs 50$ per instance which does not include dns queries that need to be done and are currently taxed now solely.
IMHO this price is not justified, so I'll drop the idea.
So AWS has the concept of traffic flow diagrams that have different types of routing / health checks and multiple other features that could be factored out based on a zone similar to a template.
The thing is that in our case the template could contain the tree that would ultimately be formed and then it could simply be linked to all zones linked to that policy.
This will aid in altering zones in bulk or limit the amount of requests needed for such an operation.
BUT there is a catch each such zone has to have a policy record created with a specific version linking it to the correct flow. This link costs 50$ per instance which does not include dns queries that need to be done and are currently taxed now solely. IMHO this price is not justified, so I'll drop the idea.