Amazon Route 53 Reviews

I use Route 53 as a global naming service. For anyone to access services with a recognizable name like PeerSpot dot com, Route 53 is a necessity. 

It is utilized not only for public access but also as a private aliasing service to secure and protect services. 

Additionally, Route 53 offers a DNS firewall to safeguard against DNS vulnerabilities.

The introduction of Route 53's DNS firewall has provided an added layer of protection, giving us peace of mind. It helps track and log DNS requests, thus preventing any potential DNS vulnerabilities and offering better security controls.

The simplicity and reliability of Route 53 make it valuable. It is cost-effective and integrates easily with other AWS services, making it simple to expose and manage services. The integration with certificate services is also seamless. 

Additionally, Route 53 is straightforward both via the console and API, providing ease of use.

I'm not a network specialist, so I don't know the deep specifics of DNS and what might need improvement on an international level. 

However, it's necessary that any improvements adhere to international ISO standards. A general area for improvement with AWS services is that while AWS quickly releases new services, sometimes these services are not as mature as expected, which can be frustrating. 

It's often advisable to wait for version two of any new service.

I have been working with Route 53 for eight years.

Route 53 is a reliable service that is always available and provides consistent performance. It does not require maintenance.

There are no limitations to the scalability of Route 53; it will scale to more than anyone will need.

There has been no need to reach out to technical support for Route 53, as it is a simple service. There is a wealth of information available online for any questions that might arise.

Positive

I have worked with Microsoft Active Directory for DNS in enterprises in the past. However, AWS services offer better automation and integration through Terraform, SDK, and APIs, making them preferable.

The initial setup of Route 53 is straightforward. It requires upfront planning for domain naming and account hierarchies to facilitate efficient deployment and management.

The implementation of Route 53 has provided essential security improvements, particularly with the DNS firewall. It logs and audits DNS requests, adding control previously missing and ensuring peace of mind.

Route 53 is very cost-effective, adding to its value proposition.

There is no real choice if you want public services to be accessible. However, I recommend using Route 53 for internal private naming spaces as well, as it centralizes management and is easy to manage.

I'd rate the solution ten 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 AWS services such as EC2, Route 53, Elastic Beanstalk, VPC, and IAM. I use Route 53 specifically for DNS and managing domains and URLs.

I have used Route 53 to integrate applications and systems across different geographic locations.

Host zones and integrated features such as Health Checks and DNS routing are valuable features of Route 53.

The number of domain types available on AWS, such as the .br domain for Brazil, should be expanded.

I have used Route 53 for a few years.

The stability of the service with Route 53 is okay, and I have not experienced any problems with stability.

Scalability is okay. Route 53 is working very well, and I have never had any problems with it.

Amazon services are very stable, and there are few problems. The professional services on AWS are very specialized, and I rarely need support.

Positive

The initial setup and deployment are more difficult.

Route 53 is more expensive. It depends on the type of feature you use, as each feature has its own distinct pricing.

I recommend the service to other people, but Brazilian users may have difficulty because the .br domain is not supported.

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

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.

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.