Amazon Route 53 Reviews

Its integration with other Amazon services is a very useful feature, in my opinion. It goes well with other Amazon services. So, when we are using other Amazon services, like customer infrastructure on an Amazon cloud, we prefer to use Amazon Route 53.

Supporting DNS check is one feature missing in the solution. The DNS check support is not there in Amazon Route 53. The aforementioned details can be considered for improvement.

Though we don't use Amazon Route 53 regularly, we use it for a couple of projects. So, it has been running for five years. My company has a partnership with Amazon.

Overall, the product is stable.

There are no such issues with the product's scalability.

Technical support from Amazon is very good, especially for those having a business support plan who get instant support. I rate the technical support a nine out of ten.

Positive

The product was also easy to deploy.

The price of the solution could be a little bit lower compared to Google DNS, which has more features than Amazon.

Overall, I rate the solution an eight out of ten.

We use Amazon Route 53 for dynamic naming and routing policy.

The solution should have a more user-friendly user interface.

I have been using Amazon Route 53 for three to four years.

Amazon Route 53 is a stable solution.

Amazon Route 53 is a scalable solution.

The solution’s initial setup is easy.

We implemented the solution through an in-house team. The solution's deployment took around 10 to 15 minutes.

I use the latest version of Amazon Route 53. Amazon Route 53 is a cloud-based solution.

I would recommend Amazon Route 53 to other users.

Overall, I rate Amazon Route 53 a nine out of ten.

Amazon Route 53 is a DNS resolution service that helps you to map your hostname to another hostname. We use it to provide custom domain names for all our AWS services that come with a cryptic URL.

I have been using Amazon Route 53 for more than one year.

Amazon Route 53 is a stable solution.

Amazon Route 53 is a scalable solution.

Amazon Route 53's initial setup is easy.

Amazon Route 53 is user-friendly for anyone who knows to work with DNS records. Otherwise, they will have to learn about the different kinds of DNS records. Two people in our company do the solution's configuration.

I would ask users to use Amazon Route 53 because I haven't faced any problems with it.

Overall, I rate Amazon Route 53 a ten out of ten.

We use the product for DNS load balancing and WAF. 

The solution offers you the flexibility to control configuration rules. 

The product should improve its automation. 

I have been working the product for two years and a half. 

I would rate the solution's stability a ten out of ten. It never went down for me. 

I would rate the tool's scalability a ten out of ten since I didn't have any problems with it. 

The product's setup is straightforward. 

We have got ROI with the tool's use since it prevented us from downtime and losing millions. 

I would rate the solution an eight out of ten. The product is better than Cloud DNS. You should use Terraform while using Cloudflare so that you do not need to create manually anything. People usually think that they will use Cloudflare less but end up using it more. The best way to go is to follow a pipeline automated process for testing and production. 

The most valuable feature of Amazon Route 53 is routing, where we can set up a DR with a different kind of routing method. The solution has a user-friendly dashboard. The solution provides good stability and availability.

The solution’s pricing and technical support could be improved.

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

Amazon Route 53 is a stable solution.

Around 90% of domains are on Amazon Route 53 because its deployment time is very low. If you update something in Amazon Route 53, it will be reflected within one minute.

Amazon Route 53 is very easy to deploy and integrate.

Amazon Route 53 is not an expensive solution.

Amazon Route 53 is deployed on the cloud in our organization. I would recommend Amazon Route 53 to other users.

Overall, I rate the solution ten out of ten.

We use Amazon Route 53 for DNS management. We're doing continuous evaluations of our policies on AWS, which is another reason why we're using Amazon Route 53.

The solution is deployed on a private cloud.

We're a startup, so less than 100 people are using this solution.

The scalability is the most valuable feature.

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.

I have used this solution for one year.

It's stable.

It's scalable.

Initial setup is simple and easy. It took a maximum of two days to deploy. When I deployed Terraform activities, it took a maximum of half an hour.

I would rate this solution as seven out of ten. 

Amazon Route 53 is for high availability and scalability. It works well in AWS and handles almost all of the queries.

My advice is to use Amazon Route 53, but you need to make sure that it's configured properly because your data and organization could be compromised.

Our primary use case is as a tool for projects that require managing the DNS.

The most valuable feature is that it works very well.

I would like to see more customization or interface options. 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.

I have been using Amazon Route 53 for the past several years.

It is absolutely stable and I have had no issues with it.

AWS's credibility is absolutely fantastic when it comes to scalability.

The initial setup is very easy and straightforward.

I would rate Amazon Route 53 a ten out of ten.