Amazon Route 53 Reviews

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.

Our company uses the solution for DNS services. We purchase domains, create load balancers, set provisions, host websites, and manage how internet traffic routes to websites. The solution handles all DNS queries and translates friendly domain names to numeric IP addresses. 

It is easy to process domain registrations. 

The solution effectively monitors the health of resources and provides good identity access management. 

The solution should include more robust and secure services for hardening sites. Amazon is a public cloud with a very rich set of security features. But, in some cases we find difficulties such as network latencies in terms of hitting particular links. 

I have used the solution across various projects in the past ten years. 

The stability is good but can be affected by a few parameters. The solution hits the load balancer and navigates to the EC2. If any web server, disc, or RAM issues happen, then stability is vulnerable. 

To maintain good stability, it is important to watch inbound and outbound load balancer traffic, check RAM and disc space, and monitor CP utilizations. If you routinely monitor your system with automations and notifications, then you will have no problems with stability. 

Stability is rated a six out of ten. 

The scalability is good so is rated a seven out of ten. 

Technical support is good and can resolve issues both from the customer side and the AWS side. Support is rated a nine out of ten. 

Positive

The setup is easy, takes less than ten minutes, and is rated a nine out of ten. 

The pricing depends on usage and is moderate. 

If you create a domain space in the solution, then you have to use it every time for projects, websites, and documentation. Your cost increases based on usage across months, days, or minutes. 

The solution is good for configuring load balancers and other items. I rate the solution an eight 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.

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.

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.

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.

The product's most valuable feature is the ability to host zones.

The platform is more complicated to learn than GoDaddy. This particular area needs improvement.

The product is stable.

If my company has 53 teams, they'll work with different clients, which varies between them. The clients' preferences mostly drive the decision to use Amazon Route 53 or other services like GoDaddy. Some may prefer services specifically designed for domain hosting, while others may consider migrating their zones or records to a cloud platform. Additionally, some clients buy domains from one provider and use Route 53 to host services on the same platform.

The initial setup was straightforward because it's done automatically on the cloud.

Amazon Route 53 is not that expensive. When I compare it with GoDaddy, it costs me almost the same. Overall, it's worth the investment.

With Route 53, you can host zones and create records, and it perfectly works with other services. You do not have to worry about providing those things manually; you can also automate these processes.

It's much easier and faster to use compared to GoDaddy. You can host your zone and name servers here, and keeping track of records is easy. Additionally, it seamlessly integrates with other AWS services. For example, using a Load Balancer record against your domain will work perfectly with Route 53.

It helps us manage everything from domain routing to subdomain routing to the mail service. With Route 53, you can also create records for SMTP servers. It's a complete solution for hosting the entire site.

I rate it a seven out of ten.