No-brainer DNS servers for the AWS Ecosystem, easy to use
September 14, 2020
No-brainer DNS servers for the AWS Ecosystem, easy to use
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Amazon Route 53
As part of our Cloud migration to AWS we have started using Route 53. Being able to programmaticaly build all aspects of the deployment in general and for route 53 in particular is a life saver. Being part of the same ecosystem make deploying so much easier... As we move all on-prem to AWS, and DNS is essential, Route 53 we need to rely on R53 and it delivers.
Pros
- Plain DNS.
- Easy to programmatically administer.
Cons
- There are a few limitations which we encountered but hope will be resolved soon.
- Not R53 speficic, but naming conventions are essential.
- Quicker deployments.
- Programmatic naming conventions.
Infoblox is the one we used on premises and briefly looked at for AWS. Route 53 however is well suited for our needs and was easier to implement. As AWS was already new for use, learning Route 53 anew made no difference in selecting it.
Do you think Amazon Route 53 delivers good value for the price?
Yes
Are you happy with Amazon Route 53's feature set?
Yes
Did Amazon Route 53 live up to sales and marketing promises?
Yes
Did implementation of Amazon Route 53 go as expected?
Yes
Would you buy Amazon Route 53 again?
Yes
Comments
Please log in to join the conversation