Try our new research platform with insights from 80,000+ expert users
Amazon Route 53 Logo

Amazon Route 53 pros and cons

4.4 out of 5

Pros & Cons summary

Buyer's Guide

Get pricing advice, tips, use cases and valuable features from real users of this product.
Get the report

Prominent pros & cons

PROS

Amazon Route 53 is highly valued for its scalability and stable performance.
It offers valuable features such as DNS, routing, and traffic management, which are crucial for effective deployment.
The health check functionality significantly enhances uptime and reliability of AWS services like EC2 and EKS.
Route mapping capabilities are appreciated for allowing customized mapping of services in alignment with business requirements.
Seamless integration with other AWS services enhances its effectiveness, making it easier to manage domains and route traffic efficiently.

CONS

Amazon Route 53 lacks support for DNS check and could enhance DNSSEC support across domain types and configurations.
There is difficulty managing Amazon Route 53 without technical knowledge, and it may not integrate easily with on-premise infrastructure.
Amazon Route 53 can be expensive as usage scales, particularly with advanced features and high query volumes.
Detailed logging and error tracing need improvement in Amazon Route 53 for intuitive monitoring and troubleshooting.
Amazon Route 53 requires better support options, including chat, to enhance user experience and resolve issues effectively.
 

Amazon Route 53 Pros review quotes

Uddeshya Kumar - PeerSpot reviewer
Product Owner at a tech vendor with 11-50 employees
Nov 23, 2022
The scalability is the most valuable feature.
Roland Nazareth - PeerSpot reviewer
Principal Consultant at a computer software company with 1,001-5,000 employees
Dec 15, 2022
The initial setup is good and straightforward.
reviewer2040105 - PeerSpot reviewer
Development Team Lead at a computer software company with 201-500 employees
Dec 21, 2022
The most valuable feature is that it works very well.
Learn what your peers think about Amazon Route 53. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,082 professionals have used our research since 2012.
Bireshwar Adhikary - PeerSpot reviewer
Senior Consultant at ATOS
Jan 20, 2023
The solution effectively monitors the health of resources and provides good identity access management.
Jonathan Pehau - PeerSpot reviewer
Infrastructure analyst specialized in cloud computing at IT2GO Solutions
Mar 9, 2023
Using Amazon Route 53 is located in a central place in Amazon AWS which makes it easier to manage every DNS entry in one place. You are able to manage your public and private DNS from there. We can create rules based on weight and globalization is impressive.
MR
Senior Site Reliability Engineer
May 5, 2023
The solution offers you the flexibility to control configuration rules.
Tarique Siddique - PeerSpot reviewer
Director - IT Infrastructure at INADEV CORPORATION
May 25, 2023
Technical support from Amazon is very good...Overall, the product is stable.
Prasanth MG - PeerSpot reviewer
Software Engineer at Readyly
Jun 30, 2023
Amazon Route 53 is a DNS resolution service that helps you to map your hostname to another hostname.
Adalberto Barbosa Da Costa Lobato - PeerSpot reviewer
Cloud Solutions Architect at gwcloud.company
Sep 7, 2023
The main DNS resolution is really, really fast.
Sameh Moamen - PeerSpot reviewer
Infrastructure Manager at Arabian Cement Company
Nov 14, 2023
It stands out for its user-friendly interface, seamless integration with other AWS services, and ability to efficiently manage DNS, making it a valuable tool for various deployment scenarios, including those involving Kubernetes on AWS.
 

Amazon Route 53 Cons review quotes

Uddeshya Kumar - PeerSpot reviewer
Product Owner at a tech vendor with 11-50 employees
Nov 23, 2022
Route 53 would be better if it had the ability to handle multiple requests at the same time because we have a lot of users. I would like that to be optimized in the next version.
Roland Nazareth - PeerSpot reviewer
Principal Consultant at a computer software company with 1,001-5,000 employees
Dec 15, 2022
There are no detailed logs, and they should implement that in the solution.
reviewer2040105 - PeerSpot reviewer
Development Team Lead at a computer software company with 201-500 employees
Dec 21, 2022
When we are looking at the model registry, it may be not clear sometimes. For example, if you use a single grid model and group or registry, it has a different SDK in the pilot. And it may be not so comfortable to use both of them because it is two different places for keeping things in order.
Learn what your peers think about Amazon Route 53. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,082 professionals have used our research since 2012.
Bireshwar Adhikary - PeerSpot reviewer
Senior Consultant at ATOS
Jan 20, 2023
The solution should include more robust and secure services for hardening sites.
Jonathan Pehau - PeerSpot reviewer
Infrastructure analyst specialized in cloud computing at IT2GO Solutions
Mar 9, 2023
It may not always be easy to integrate with on-premise infrastructure, especially with the complexity of the resolver and other factors involved. Improvements could be made to enhance the ability to integrate seamlessly.
MR
Senior Site Reliability Engineer
May 5, 2023
The product should improve its automation.
Tarique Siddique - PeerSpot reviewer
Director - IT Infrastructure at INADEV CORPORATION
May 25, 2023
Supporting DNS check is one feature missing in the solution.
Prasanth MG - PeerSpot reviewer
Software Engineer at Readyly
Jun 30, 2023
When you add a new DNS record instructing the solution to map one thing to another, it has to propagate to all the networks, which takes some time.
Adalberto Barbosa Da Costa Lobato - PeerSpot reviewer
Cloud Solutions Architect at gwcloud.company
Sep 7, 2023
The product could improve its price.
Sameh Moamen - PeerSpot reviewer
Infrastructure Manager at Arabian Cement Company
Nov 14, 2023
Streamlining and optimizing processes related to Procter, VPN workflows, and other subjects based on specific needs would allow for continual improvement and adaptation to the evolving requirements of the system.