Amazon Route 53 Reviews

We use Amazon Route 53 primarily for routing purposes when trying to route to different environments.

During migration, if you want requests to move towards on-premises versus when you're trying to have DNS resolution done on cloud, the features in Route 53 are really good. We also love the health check features.

There are no detailed logs, and they should implement that in the solution.

We have been using this solution for quite some time.

It is a stable solution. However, I haven't used the solution extensively in the production environment, and we have not bombarded it with the load to see the results.

It is scalable. 

The initial setup is good and straightforward.

I rate the solution an eight out of ten. It is a pretty good solution. Genesys routing also plays a significant role, so I think this should be part of the solution.

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.

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.