Amazon Route 53 Reviews

Businesses often use Route 53 for intelligent traffic routing, such as directing users to the nearest data center using geolocation routing or balancing loads across multiple servers with weighted routing.

Companies implement Route 53's health checks to ensure high availability. If a primary resource becomes unhealthy, Route 53 can automatically redirect traffic to a backup resource.

Many users leverage Route 53 to manage DNS for websites hosted on AWS services like EC2 or S3. It allows easy configuration of domain names, SSL certificates, and routing policies.

Amazon Route 53 is easy to manage and seamlessly integrates with other AWS services.

The pricing structure is complex, especially with multiple components like query pricing, health checks, and traffic flow. Enhancements to the UI are needed for easier navigation and management would improve the user experience. Simplifying the pricing model or providing clearer cost estimators could help.

Route 53 supports DNSSEC, and it may not be available for all domain types or configurations. It can become expensive as usage scales, especially with advanced features and high query volumes. Slower response time with lower-tier support plan.

I have been working with Amazon Route 53 for approximately from 2021.

Service downtime can be a challenge, however, it is not specific to Amazon Route 53. It involves broader service interruptions. Features like latency-based routing and geolocation routing enable effective traffic distribution based on user location and application performance, further supporting scalability.

Amazon Route 53 is highly scalable, making it suitable for a wide range of applications, from small websites to large enterprise systems.

Customer service and support for Amazon Route 53 typically reflect the overall AWS support experience. If you have low support plan then experience longer response times, which can be frustrating in critical situations

Positive

Cloudflare is used with basic DNS management, DDoS protection, and performance optimization. But when you move infrastructure on AWS then Switch on Route 53.

Initial setup of Amazon Route 53 can vary in complexity depending on your specific needs and familiarity with DNS services. Advanced Routing Policies,
Health Checks and Monitoring, Domain registration process and configuaration add the complexity.

We implemented the solution in-house.

I am not involved with the pricing as it's a company policy, so I am not aware of the actual costs. But its pricing structure is complex

Wwe also evaluate Cloudflare DNS and Microsoft Azure DNS.

Amazon Route 53 is a powerful DNS service. Integrate with AWS and Non-AWS Services.

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.

For Route 53, I use it for DNS purposes. I give addresses to my services and protect some of my services with it, especially those with production layers that cannot be accessed directly. I serve different endpoints and use Route 53 to ensure that services are only accessed with appropriate security settings.

Route 53 allows me to standardize addressing and make it more memorable, which helps in identifying services more quickly.

The route mapping feature of Route 53 is valuable as it allows me to map services according to our requirements. This standardizes our address system.

Error tracing could be made more intuitive. They could include rules that affect the route analysis, making tracing easier and smoother.

I've only worked with it for several months since I have been using it in my new company.

As long as I have been using it, I haven't really faced any problems with it. I have not experienced any outages or downtime. Everything's been pretty stable.

The scalability is maintained by AKS, and Route 53's scalability part is primarily involved with load balancing. I don't have much knowledge beyond this, but it's mostly related to load balancing since many users access it.

I haven't really interacted with the technical support, so I cannot give a rating on that.

The setup is not difficult. I followed guidelines provided by AWS and some tutorials to replicate the process. Fortunately, the process didn't have many problems other than the issue with trace analysis.

Not that much, maybe two or three people who have the current knowledge, as I am new here.

The ROI is pretty fine, but it could be improved. Currently, I haven't seen any tangible return on investment yet.

I haven't compared it to other cloud services, so I cannot give a precise evaluation. The pricing options are good for now.

Try to understand the concepts of DNS with Route 53 and go through the documentation as it helps with the initial configuration.

I'd rate the solution eight 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.

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.

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.

I am using Amazon Route 53 as a DNS service to host and manage domain names. My role includes configuring instances, load balancers, and managing network configurations.

Route 53 provides a reliable and scalable DNS service, allowing us to host applications and manage domain names effectively. The integration with other AWS services enhances our infrastructure and supports seamless deployments.

Amazon Route 53 is beneficial for managing traffic and domain names, offering features like latency-based routing and multi-deployment options. Its user-friendly interface and compatibility with other AWS services make it valuable.

There could be improvements in the configuration process, particularly in the options provided during setup, such as subdomain configurations and certificate management.

I have been working with Amazon Route 53 since I joined the company in July 2023, which is approximately one and a half years.

The solution is stable. We use auto-scaling groups to manage load and have not faced significant downtime due to its reliability.

Amazon Route 53 scales well with our needs. We haven't faced any scalability issues, thanks to its integration with AWS services.

I have not needed to reach out to AWS technical support often since I handle tasks from scratch and resolve issues internally.

Positive

Before Route 53, the team used web hosting services like cPanel, Web Host, or HostGator for domain and application hosting.

The initial setup involves purchasing and configuring domain names and name servers. It requires understanding DNS management and can be completed quickly if done correctly.

I am the only cloud and DevOps engineer managing Route 53 in our organization.

While I don't have exact ROI figures, we choose Route 53 for its well-integrated and high-quality service, even if it costs slightly more.

The pricing of Route 53 is slightly higher compared to other services, however, it is justified by its high availability and reliability.

I recommend using Amazon Route 53 because of its user-friendly interface and its security features. I am also available to assist others from scratch.

I'd rate the solution nine out of ten.