Route 53
January 25, 2023

Route 53

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Amazon Route 53

Ease of use and management of the amazon route 53 that is our main benefit. Our current solution was not cloud based and it would affect us geographically. But Route 53 being a cloud service has greatly helped us in that space. We use it for managing the external DNS services within our organization.
  • It help us increase dependability by rerouting our DNS to an alternate destination if the original application endpoint becomes unavailable.
  • Amazon Route 53 on Amazon Traffic Flow directs the traffic depending on a variety of factors, including endpoint health, geographic location, and latency which we set up various traffic regulations and choose which ones to use at any given moment.
  • We can build and change traffic policies via the Route 53 interface, AWS SDKs, or the Route 53 API using the easy visual editor So, the versioning function in Traffic Flow keeps track of changes to traffic policies, allowing us to quickly roll back to a prior version through the interface or API and thus it provides flexibility.
  • more customization or interface options
  • Model registry may be not clear sometimes.
  • Routing users to the closest or best-performing resources: Route 53 allows you to use geolocation and latency-based routing to route users to the resources that will give them the best performance.
  • Load balancing: Route 53 can be used to distribute incoming traffic across multiple resources, such as Amazon Elastic Compute Cloud (EC2) instances or Amazon Elastic Container Service (ECS) tasks, to improve the availability and scalability of your application.
  • Managing domain names: Route 53 can be used to register domain names and manage DNS records, making it a one-stop solution for managing your domain name and routing traffic to your resources.
  • by providing a highly available and scalable DNS service that can improve the availability, scalability, and performance of the organization's applications. This can lead to increased customer satisfaction, reduced costs associated with managing and scaling infrastructure, and increased revenue.

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

SecureCRT, Wireshark, SolarWinds IP Address Manager (IPAM)
- Routing users to the closest or best-performing resources: Route 53 allows you to use geolocation and latency-based routing to route users to the resources that will give them the best performance.
- Load balancing: Route 53 can be used to distribute incoming traffic across multiple resources, such as Amazon Elastic Compute Cloud (EC2) instances or Amazon Elastic Container Service (ECS) tasks, to improve the availability and scalability of your application.
- Managing domain names: Route 53 can be used to register domain names and manage DNS records, making it a one-stop solution for managing your domain name and routing traffic to your resources.

Scenarios where Route 53 is less appropriate include:Applications with very high query rates: Route 53 is designed to handle millions of queries per second, but if your application generates an extremely high query rate, you may need to use a specialized DNS service.Applications that require very low latency: Route 53 is designed to provide low-latency DNS service, but if your application requires ultra-low latency, you may need to use a specialized DNS service or a self-hosted DNS solution.Applications that require advanced security features: Route 53 provides basic security features such as DNSSEC, but if your application requires advanced security features such as DDoS protection, you may need to use a specialized DNS service.