Amazon Route 53: Simple Powerful DNS at Your Fingertips
September 21, 2020

Amazon Route 53: Simple Powerful DNS at Your Fingertips

Matthew Lauber | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Amazon Route 53

We use Amazon Route 53 for managing client and company domains for a site-hosting provider in the Human Resources market. We host a variety of sites for clients and use Route 53 to manage DNS records for the sites we're hosting. We also use it to manage our internal services hosted on AWS.
  • Simple
  • Industry Leader
  • Integrates well with AWS ecosystem
  • Rate limits are low
  • UI doesn't scale well to large numbers of hosted zones.
  • Hard to transition from
  • Faster deployment/rollout
  • Individualized customer configuration
  • Rate limits leading to delays
We selected Amazon Route 53 because we were looking for a tool that integrated well with our existing AWS infrastructure. Route 53 is industry-leading and worked well for our initial use case, that being individual client sites pointing a the same static IP. However, as our infrastructure grew, and became more dynamic, the rate limits on Route 53 limited how well our tools could manage those DNS updates.
The Amazon support staff for Route 53 are knowledgeable and understood our problems. Those that we ran into that fit the expected use case were easily dealt with by them. However, feature improvements for large numbers of domains, especially around the user interface and APIs were slow, and API rate limits remain an issue.
Amazon Route 53 is designed well, with individual domains easily configurable, and with the current state available at a glance. The UI does have scaling issues, but they are at scales most companies will not encounter. The tooling surrounding Route 53 in AWS is very good and makes use of Route 53 for many features.

Do you think Amazon Route 53 delivers good value for the price?


Are you happy with Amazon Route 53's feature set?


Did Amazon Route 53 live up to sales and marketing promises?


Did implementation of Amazon Route 53 go as expected?


Would you buy Amazon Route 53 again?


Amazon Elastic Compute Cloud (EC2), Amazon Elastic Container Service (Amazon ECS), Kubernetes
So, my recommendation for Amazon Route 53 is actually very different depending on the use case. If you're looking for a tool to handle hundreds of domains/records, then it's a wonderful tool, probably a 9 out of 10, especially if you're doing static routes. However, if you're updating routes often, or hosting lots of domains, the rate limits can be extremely limiting.