Amazon Route 53 Reviews

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.

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 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.

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.

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. 

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.

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.

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.