Amazon Route 53 Reviews

I use the solution in my company to create or set up DNS for some projects.

The most valuable feature of the solution stems from its ability to help our company in the area of top-level domains, specifically generic top-level domains, and geographic top-level domains, which helps resolve DNS queries and use the hosted zone, which allows us to adjust the DNS part.

It is difficult to manage the product if the person involved in the setup process doesn't know much about the solution. From an improvement perspective, the product should be easy for everyone to understand.

I have experience with Amazon Route 53. I am a customer of the tool.

Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution an eight out of ten.

For the web applications, the employees in our company need Amazon Route 53 to deal with the area of DNS. The product helps users assign the DNS to a particular IP address.

The product's initial setup phase was easy. The product is easy to manage for those who know about the product.

The price of the product is perfectly fine in my opinion.

The product can be used for DNS management if a user connects the DNS name with Amazon Route 53. The tool can be used for DNS-related purposes.

The product helps our company set up and register domain names. The tool also helps our company to add a domain name address to a website on the browser.

The product helps with the traffic flow feature as it allows you to assign CIDR blocks and IP addresses. The tool also helps in the area of DNS queries.

The product integrates with other services from AWS, like Amazon S3 bucket and load balancers. The product can also be used with AWS EC2 Instances, AWS Global Accelerator, Amazon SNS, and AWS Lambda.

I recommend the product to those who plan to use it. In our company, we use the services of the product without any cloud products.

I rate the overall tool an eight out of ten.

I use the solution in my company for internet monitoring.

In my company, we are running some trials to see if Amazon Route 53 works well and to compare other internet monitoring solutions. So far, Amazon Route 53 looks fine.

The limitations of the tool revolve around the area of monitoring location, especially since the performance and selection options offered by the product are limited.

I have been using Amazon Route 53 for a year. I am just a customer of the solution.

It is a stable solution.

It is a scalable solution. The scalability should be good.

I use a basic plan for technical support for the solution. My company really does not get hands-on support from Amazon. There is not sufficient information in the area of support unless you go for a higher pay plan to get more support. I rate the technical support a six out of ten.

Neutral

I am actively working on Docker, Kubernetes, and VMware, but not really in-depth. I am on the information security team, supporting different kinds of software and solutions. On the other hand, I use some tools for personal interest. I always browse through different product solutions and look for updates, etc.

I use quite a little bit of everything, but not in-depth. I didn't really come up with any particular solutions. I just tried out some AWS tools, like Route 53 and CloudWatch.

The product's initial setup phase is straightforward, especially since it is a web service, so we don't need to do any installations. There are more than a few clicks required to install the tool, but still, it is okay to follow the instructions and run the product.

The solution can be deployed in just a few minutes.

I don't handle the billing part of the tool.

The tool's health check functionality improved our company's service reliability since it is a good feature. Its use still depends on a case-by-case configuration. The tool has certainly fulfilled the basic purpose of monitoring.

There is no need to somehow maintain or support the solution.

I am not sure how Amazon Route 53 can handle traffic spikes and what difference it has made to our company's service availability.

The tool is not difficult to use, and it does what it is meant to do.

I rate the tool an eight out of ten.

Our primary use case for Amazon Route 53 revolves around its robust domain name system (DNS) management capabilities, supporting a diverse set of parameters and records within our environment. We extensively use Route 53 for managing various record types, including A records, MX records, and CNAME records.

The product’s security and disaster recovery features need enhancement. Additionally, they charge higher prices than other platforms. They could reduce the pricing.

We have been using Amazon Route 53 for three or four years.

I rate the platform’s stability a nine out of ten.

The product has good scalability. However, it is costlier than GCP and other cloud platforms.

The initial setup is easy. The deployment process is similar to making entries in Google Forms. It takes five minutes to complete.

For traffic management, the product offers functions similar to other domain name server providers. As an AWS user, having Route 53 as an in-house tool simplifies the entire process, eliminating the need to navigate different platforms for defining the records or other entries. The integration within the AWS ecosystem streamlines the management of DNS services.

The most beneficial feature of Route 53 for domain registration, from the engineers' perspective, lies in its seamless integration within the AWS Cloud ecosystem. It becomes easier to manage multiple AWS services in a single platform.

The feature for health check efficiently impacts the uptime and reliability of AWS servers including EC2 and EKS. It enables easier traffic routing as compared to GoDaddy.

The readiness checks feature ensures that our applications are well-prepared to handle incoming traffic including DNS firewall setup. Also, we can conduct geo-based and latency-based routing. For IT-based routing, they offer a DNS failover feature.

I recommend the product to others and rate it a nine out of ten.

Our primary focus is on migrating from an on-premises infrastructure to a cloud-based solution. This entails handling multiple versions of modern applications, with a specific emphasis on cloud support, especially for API functionalities.

The ability to customize parameters for health checks within Amazon Route 53 enhances control and precision in system configurations, contributing to a more reliable and tailored deployment experience.

It stands out for its user-friendly interface, seamless integration with other AWS services, and ability to efficiently manage DNS, making it a valuable tool for various deployment scenarios, including those involving Kubernetes on AWS.

Streamlining and optimizing processes related to Procter, VPN workflows, and other subjects based on specific needs would allow for continual improvement and adaptation to the evolving requirements of the system.

I have been using it for three years.

I find it to be highly stable and reliable.

It offers good scalability abilities.

Technical support is highly dependent on the service. Each user equipment, excluding those under protection, falls within this range.

Most of our operations are centralized through a Microsoft domain controller. We've established connections among Microsoft servers and implemented rules governing communication. This setup is particularly crucial when there's a need to communicate with servers across various sites or establish connections between smaller data sites within the company.

Overall, I would rate it nine out of ten.

Amazon Route 53 provided the solution we needed to manage servers.

The solution is used to manage servers, and its interface is easy to use.

Since DNS is based on internet access, improving some security features would improve internet quality worldwide.

I have been using Amazon Route 53 for ten years.

I rate the solution’s stability ten out of ten.

Amazon Route 53 is a very scalable solution.

I rate the solution’s scalability ten out of ten.

The solution's technical support team is knowledgeable and respects SLAs.

Positive

I have previously used Cloudflare. I prefer Cloudflare over Amazon Route 53 because of my familiarity with it, as I have used it for a long time.

The solution’s initial setup is easy.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution’s initial setup a nine or ten out of ten.

The solution’s deployment was very quick.

I would recommend Amazon Route 53 to other users because it can concentrate every configuration on the same platform.

Overall, I rate the solution ten 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.

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.