Amazon Route 53 Reviews

We've purchased most of our domains through AWS and manage our certificates there as well. 

Route 53 handles most of our domain-related configurations and DNS records. We don't rely on any other external DNS providers like GoDaddy.

Since we're already in the AWS cloud, it makes sense to use their DNS provider rather than a third-party solution.

The documentation is clear and should be easy to understand. For basic concepts, Route 53 has good guides and white papers for layman's concepts. So it is easy to get started with.

You can manage it manually or use third-party tools like Terraform or CloudFormation templates.

Since we're already in the AWS cloud, it makes sense to use their DNS provider rather than a third-party solution. Route 53 is not available for Kubernetes like Google Cloud DNS, but we can import records.

Hopefully, Amazon will add that functionality in the future. The convenience of having our domain management integrated within AWS is the main advantage.

I've been using Route 53 for the past five years.

We haven't faced any outages or issues directly related to Route 53. It has been 100% stable for me. 

Most of our clients use Route 53. More than ten clients actively work with it.

We have contacted support, though it might not have been specifically for Route 53. 

We have a premium AWS account, and their support is awesome. Compared to other cloud providers, I'd rate AWS support as good.

We use several services like EC2, VPC, AWS Lambda, AWS API Gateway, Route 53, CloudFront, and others.

Since we're already in the AWS cloud, it makes sense to use their DNS service rather than a third party. It simplifies management and billing to keep everything within AWS.

For example, for certificate renewal, we can set up alerts. If someone forgets to renew the certificate, automation helps remove the chance of outage. 

For initial setup, we generally use provisioning tools for these kinds of DNS records. The choice often depends on the cloud provider and the Infrastructure as Code (IAC) tools the client prefers. We adapt our approach accordingly rather than focusing on a single method within Route 53.

The documentation is very user-friendly. Even someone with no prior experience can easily understand it. It provides step-by-step instructions and explains things in a clear and concise way. You can find everything you need to know about Route 53 and its features in the documentation, including white papers.

In addition to manual configuration, you can also use third-party tools like Terraform, Pulumi, or AWS CloudFormation templates to manage your Route 53 configurations.

It can be expensive compared to some other providers. You can estimate the costs using the AWS pricing calculator.

From my experience, Route 53 meets most of our needs. I'm satisfied with its performance.

If you need to start using it in AWS, first, you have to purchase a domain. Then, if you want to set up SSL/TLS, you can purchase a certificate from AWS Certificate Manager and integrate it with your service, whether it's on Elastic Beanstalk, EC2, EKS, or anything else. 

Route 53 documentation is available, or the AWS support team can help you set things up.

Overall, I would rate the solution a nine out of ten. 

I use AWS services such as EC2, Route 53, Elastic Beanstalk, VPC, and IAM. I use Route 53 specifically for DNS and managing domains and URLs.

I have used Route 53 to integrate applications and systems across different geographic locations.

Host zones and integrated features such as Health Checks and DNS routing are valuable features of Route 53.

The number of domain types available on AWS, such as the .br domain for Brazil, should be expanded.

I have used Route 53 for a few years.

The stability of the service with Route 53 is okay, and I have not experienced any problems with stability.

Scalability is okay. Route 53 is working very well, and I have never had any problems with it.

Amazon services are very stable, and there are few problems. The professional services on AWS are very specialized, and I rarely need support.

Positive

The initial setup and deployment are more difficult.

Route 53 is more expensive. It depends on the type of feature you use, as each feature has its own distinct pricing.

I recommend the service to other people, but Brazilian users may have difficulty because the .br domain is not supported.

I'd rate the solution eight out of ten.

I use Route 53 as a global naming service. For anyone to access services with a recognizable name like PeerSpot dot com, Route 53 is a necessity. 

It is utilized not only for public access but also as a private aliasing service to secure and protect services. 

Additionally, Route 53 offers a DNS firewall to safeguard against DNS vulnerabilities.

The introduction of Route 53's DNS firewall has provided an added layer of protection, giving us peace of mind. It helps track and log DNS requests, thus preventing any potential DNS vulnerabilities and offering better security controls.

The simplicity and reliability of Route 53 make it valuable. It is cost-effective and integrates easily with other AWS services, making it simple to expose and manage services. The integration with certificate services is also seamless. 

Additionally, Route 53 is straightforward both via the console and API, providing ease of use.

I'm not a network specialist, so I don't know the deep specifics of DNS and what might need improvement on an international level. 

However, it's necessary that any improvements adhere to international ISO standards. A general area for improvement with AWS services is that while AWS quickly releases new services, sometimes these services are not as mature as expected, which can be frustrating. 

It's often advisable to wait for version two of any new service.

I have been working with Route 53 for eight years.

Route 53 is a reliable service that is always available and provides consistent performance. It does not require maintenance.

There are no limitations to the scalability of Route 53; it will scale to more than anyone will need.

There has been no need to reach out to technical support for Route 53, as it is a simple service. There is a wealth of information available online for any questions that might arise.

Positive

I have worked with Microsoft Active Directory for DNS in enterprises in the past. However, AWS services offer better automation and integration through Terraform, SDK, and APIs, making them preferable.

The initial setup of Route 53 is straightforward. It requires upfront planning for domain naming and account hierarchies to facilitate efficient deployment and management.

The implementation of Route 53 has provided essential security improvements, particularly with the DNS firewall. It logs and audits DNS requests, adding control previously missing and ensuring peace of mind.

Route 53 is very cost-effective, adding to its value proposition.

There is no real choice if you want public services to be accessible. However, I recommend using Route 53 for internal private naming spaces as well, as it centralizes management and is easy to manage.

I'd rate the solution ten out of ten.

Actually, we are deploying our website in AWS as it is easy to install, and we are also hosting our domain on Amazon Route 53.

We are using AWS for our company's in-house projects. We have deployed Amazon Route 53 for our in-house website and for some other websites. Actually, we have deployed our domains with the tool. We have a company domain, and we have hosted that domain on Amazon Route 53.

Amazon Route 53 is easy to manage and install. It is also useful when hosting our websites, and it becomes easy to manage the domains with its help. The tool offers Amazon Q Business, where we install the VoIP functionalities.

For the past one and a half years, I have not seen any misconfiguration or any error in AWS. The tool works properly. The tool's handling part is a little bit more complex than Azure. Apart from maintenance, if you are managing AWS, you need to have good experience handling the tool in the past. If one doesn't have any experience with the tool in the past, then it becomes a matter of concern.

The tool's support services lack chat options offered to users, making it an area where improvements are required.

I have a year and a half of experience with Amazon Route 53. I use the tool in my company.

It is not 100 percent stable, but a 99.99 percent stable tool. Sometimes, a global error impacts the tool's services.

It is an easily scalable solution. If I have the tool installed, it is easy to install its higher versions. We are also using RDS services to install SQL DB. We are using the SQL DB to store our company data in AWS.

The solution's technical support is similar to the support services offered by Azure. Compared to AWS, it is easier in Azure to get a quick response from the technical team. I rate the technical support a seven out of ten.

Neutral

The product's installation phase is easy. It is also easy to maintain the domains in the tool. Everything with the tool is about having good knowledge of it. You should know how to handle networking or create a security group in AWS.

I am the only person who handles AWS in our company because of my knowledge of the tool. With the tool, it is much easier to manage and host the whole domains.

The solution can be deployed in a few hours.

The tool helps with the time-saving part since I am the only person handling the product. If there is some other solution in the company, then a person who can handle such a product will need to be appointed. As I manage AWS, I see that it offers users time-saving and cost-saving benefits of around 20 to 25 percent.

The tool is a bit expensive.

The health check features in the tool are good. In our company, we just add the health check, and the tool provides day-to-day health checks and reports to us to check whether our domain is working or not.

It is very easy to handle traffic spikes during peak periods using the tool. I think we have not found any bug or any error in the tool.

Currently, I haven't seen any AI features in the tool. I don't think there is a need for any AI in the tool.

I rate the tool a nine out of ten.

We use Amazon Route 53 for DNS mapping.

The most valuable features of the solution are the DNS, routing, and traffic features.

The solution’s pricing could be reduced.

I have been using Amazon Route 53 for more than eight years.

I have never faced any issues with the solution’s stability.

Around 50 people are using the solution in our organization.

I rate the solution ten out of ten for scalability.

The solution’s technical support is good.

Positive

The solution’s initial setup is easy.

Amazon Route 53 is an expensive solution. Purchasing a domain from Amazon Route 53 comes at a high cost.

We expose DNS to the public, and based on that, we use Amazon Route 53 in our load balancer. Amazon Route 53 provides good traffic management. If we change the IP of any VMs or server to a specific DNS, it gets automatically updated within a time frame and gives a very good exposure to the public.

The solution's A record and CNAME record are the most beneficial features for domain registration and management. The solution's health check feature is good because it keeps checking the health of the service. The solution integrates well with other AWS services, load balancers, VMs, or EC2 instances. I would recommend Amazon Route 53 to other users because it is a good tool for traffic flow and DNS mapping.

Overall, I rate the solution ten out of ten.

The solution is used for DNS management of applications running primarily on AWS.

I'm doing a migration from on-premise to the cloud. We’re using Cloudflare. I am migrating from Cloudflare to Amazon Route 53. It is easy to integrate with the rest of the tools, like CloudFormation.

The DNS failover and latency-based routing features are good. The solution is cost-effective. Route 53 provides flexibility in using features.

The cost calculator for determining the cost of Route 53 is a little bit obscure. It is not straightforward. It’s difficult to model the cost. The cost calculator must be improved. The product must improve its analytics features.

I have been using the solution for three years.

The tool is stable. I rate the stability a ten out of ten.

The tool is very scalable. I rate the scalability a nine out of ten. The current business I'm helping has four administrators of AWS using Amazon Route 53.

The initial setup is very easy. I rate the ease of setup a nine or ten out of ten.

We pay per use. There is no flat fee. We had to pay upfront for Cloudflare. A flat fee is easy, but it might not be cost-effective. There might have been many services that we were not using. Amazon Route 53’s price is competitive. The price is purely volume-based. 

It is nice because we need not pay much if our traffic is reduced. The solution could be expensive for some sites with huge demands. However, we can model it accurately since it is a pay-per-use model. It scales with our revenue.

It is the first time I did a migration. Overall, I rate the solution a nine out of ten.

Businesses often use Route 53 for intelligent traffic routing, such as directing users to the nearest data center using geolocation routing or balancing loads across multiple servers with weighted routing.

Companies implement Route 53's health checks to ensure high availability. If a primary resource becomes unhealthy, Route 53 can automatically redirect traffic to a backup resource.

Many users leverage Route 53 to manage DNS for websites hosted on AWS services like EC2 or S3. It allows easy configuration of domain names, SSL certificates, and routing policies.

Amazon Route 53 is easy to manage and seamlessly integrates with other AWS services.

The pricing structure is complex, especially with multiple components like query pricing, health checks, and traffic flow. Enhancements to the UI are needed for easier navigation and management would improve the user experience. Simplifying the pricing model or providing clearer cost estimators could help.

Route 53 supports DNSSEC, and it may not be available for all domain types or configurations. It can become expensive as usage scales, especially with advanced features and high query volumes. Slower response time with lower-tier support plan.

I have been working with Amazon Route 53 for approximately from 2021.

Service downtime can be a challenge, however, it is not specific to Amazon Route 53. It involves broader service interruptions. Features like latency-based routing and geolocation routing enable effective traffic distribution based on user location and application performance, further supporting scalability.

Amazon Route 53 is highly scalable, making it suitable for a wide range of applications, from small websites to large enterprise systems.

Customer service and support for Amazon Route 53 typically reflect the overall AWS support experience. If you have low support plan then experience longer response times, which can be frustrating in critical situations

Cloudflare is used with basic DNS management, DDoS protection, and performance optimization. But when you move infrastructure on AWS then Switch on Route 53.

Initial setup of Amazon Route 53 can vary in complexity depending on your specific needs and familiarity with DNS services. Advanced Routing Policies,
Health Checks and Monitoring, Domain registration process and configuaration add the complexity.

We implemented the solution in-house.

I am not involved with the pricing as it's a company policy, so I am not aware of the actual costs. But its pricing structure is complex

Wwe also evaluate Cloudflare DNS and Microsoft Azure DNS.

Amazon Route 53 is a powerful DNS service. Integrate with AWS and Non-AWS Services.

I can use Route 53 to connect my website to the Internet, which I upload on AWS. In terms of traffic management, Route 53 provides auto-scaling for performance and maintenance. It allows for good performance and maintenance of a website and improves the user experience.

Route 53 offers auto-scaling, and it is more secure than other services. It provides a reliable way to route user's websites to the Internet globally.

As per my knowledge, I can use Route 53 only for Internet purposes, and I haven't explored it much. So I currently do not see any areas for improvement.

I have been working with Route 53 for approximately one to two weeks.

Route 53 is very stable compared to other services because it is more secure. It allows safe Internet access without the risk of data leaks or hacking.

Route 53 can provide us with auto-scaling, making it scalable and beneficial for projects with dynamic requirements.

I have not faced any issues requiring tech support, so I have not interacted with their customer service.

Positive

The initial setup is straightforward.

I don't use any other vendors for DNS services. I only use OpenGate VPN for testing purposes.

I definitely recommend Route 53 to other users because it provides easy maintenance and Internet access to AWS. It also offers auto-scaling.

I would rate it a nine out of ten.

I use the solution in my company to route our applications to different domain names and IPs.

The tool's most valuable feature is in the area of domain registration and routing DNS.

Compared to Amazon, it is easy to find what you want in Azure and implement them. With Amazon Route 53, finding what you want is so much more difficult, making it an area where improvements are required.

I have been using Amazon Route 53 for two years. My company is a customer of the tool.

It is a highly scalable solution.

It is a highly scalable solution.

The technical support for the solution is very good. I rate the technical support a nine out of ten.

Positive

I use AWS and Azure. Under AWS, I use RDS, EC2, and Amazon EKS. I also use load balancers and S3.

The product's initial setup phase is easy.

It is easy to use the tool.

I rate the solution an eight out of ten.

Kubernetes is engraved in Amazon Route 53. In my company, we have created records using Amazon Route 53. It is possible to integrate Amazon Route 53 as the DNS service.

In our company, the most valuable features of the solution stem from the fact that we were able to provide our applications through the internet. The tool creates the DNS, which exposes our company's application to end users.

There are many routing policies present in the product. Currently, I use the simple routing policy and geolocation routing policy. The multiple routing policies present in the product have certain shortcomings where improvements are required.

I have been using Amazon Route 53 for five months. I am a customer of the tool.

There are some breakdowns in Amazon Route 53, and because of that, my company needs to look into Amazon EKS.

Scalability-wise, I rate the solution a seven out of ten.

Each time our company does the monitoring of applications, we know that we have set up some special values for applications. We can use the scalability option after 50 to 80 percent of our company's application is used.

The product's initial setup phase was very easy. My company needs to get the IT team to configure the load balancer, after which it is given to the DNS, which is set up on Amazon Route 53.

The solution can be deployed in ten to fifteen minutes.

For traffic management, I have been using different routing policies, like single routing policies and geolocation routing policies, as the routing policies in Amazon Route 53.

The benefits of the use of the traffic flow feature of the tool stem from the fact that we use it in our company's load balancer. In an application, if I have given 1,000 requests for a server, with the help of auto-scaling and load balancer, our company can manage 1,001 end users and the traffic.

The product can be integrated with other AWS services using IAM roles and policies. The IAM role is useful for integrating all the services in AWS.

I recommended the product to those who plan to use it.

I rate the tool a seven out of ten.