Amazon Route 53 is a Cloud Domain Name System (DNS) offered by Amazon AWS as a reliable way to route visitors to web applications and other site traffic to locations within a company's infrastructure, which can be configured to monitor the health and performance of traffic and endpoints in the network.
$0.40
Per Zone Per Month
SolarWinds IP Address Manager (IPAM)
Score 7.7 out of 10
N/A
Austin-based SolarWinds offers Internet Protocal address management (IPAM) networking service.
N/A
Pricing
Amazon Route 53
SolarWinds IP Address Manager (IPAM)
Editions & Modules
Standard
$0.40
Per Zone Per Month
Queries
$0.60
Per Million Queries
No answers on this topic
Offerings
Pricing Offerings
Amazon Route 53
SolarWinds IP Address Manager (IPAM)
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
SolarWinds professional support is included to help customers on active maintenance 7 days a week, 365 days a year.
- Routing users to the closest or best-performing resources: Route 53 allows you to use geolocation and latency-based routing to route users to the resources that will give them the best performance. - Load balancing: Route 53 can be used to distribute incoming traffic across multiple resources, such as Amazon Elastic Compute Cloud (EC2) instances or Amazon Elastic Container Service (ECS) tasks, to improve the availability and scalability of your application. - Managing domain names: Route 53 can be used to register domain names and manage DNS records, making it a one-stop solution for managing your domain name and routing traffic to your resources. Scenarios where Route 53 is less appropriate include:Applications with very high query rates: Route 53 is designed to handle millions of queries per second, but if your application generates an extremely high query rate, you may need to use a specialized DNS service.Applications that require very low latency: Route 53 is designed to provide low-latency DNS service, but if your application requires ultra-low latency, you may need to use a specialized DNS service or a self-hosted DNS solution.Applications that require advanced security features: Route 53 provides basic security features such as DNSSEC, but if your application requires advanced security features such as DDoS protection, you may need to use a specialized DNS service.
SolarWinds IP Address Manager is very useful the bigger and more complex the environment. Smaller organizations will have to consider the cost as it provides little benefit over monitoring maybe 2-3 servers. But I have over 24 DHCP servers with on average 15 subnets each so tracking and monitoring all that was very time-consuming. As a result, it was generally ignored until there was an issue. With SolarWinds IP Address Manager, I was able to set alerts to monitor scope utilization and duplicate IP addresses.
Uptime - Route53 is highly performant and available. We have had only 3-4 instances in the last 12 years when we had any downtime or outages due to Route53.
Extensive API layer on Route53 that allows integration with external tools and SDK's (Boto, Terraform, etc)
Closely integrated with the other AWS services. Makes it easy to operate the infra.
With IPAM automated address scanning, we can be confident that we are looking at an up-to-date, accurate snapshot of our network.
The built-in alerts are a great safety net. We know that even if we aren't paying close attention to our IP address space, IPAM is. If a range is nearly full, IPAM lets us know before it becomes a real problem.
IPAM's event logging gives us insight into any and all changes made by our network engineers.
During initial setup when you are using Route 53 or DNS systems for very first time, there are little number of documentation from AWS which is kinda of little tough. But, once you get hold of it, its a cake walk for everyone.
Health checks are kinda of little costly when Compared to other big players, but that doesn't affect much when you compare its uses.
The user experience is not as intuitive as other products. We have to be more restrictive around level 1 help desk access compared to NCM or NPM in SolarWinds.
Making and enforcing changes, not just monitoring, has been hit or miss in some instances.
We are heavily invested in SolarWinds. We currently own Network Performance Monitor, Netflow Traffic Analyzer, User Device Tracker, Server Application Monitor and Network Configuration Manager. We have NOC mode setup for deskside support for monitoring any down devices that may effect our network across the globe. This application gives us the information we need when we need it.
You need to know what DNS is; this is a tool built for developers who already know the technology and are just looking for a DNS management tool. The tool is very usable given that. If you're not familiar with DNS, Route53 isn't really for you and you won't find it to be very usable-- you'll need to go read the documentation, and that will start with learning what DNS is
SolarWinds IPAM is like what SolarWinds itself says, i.e. easy to use and simple. SolarWinds has really made their orion and non-orion platform products so simple that any newbie can give a try and make the best use out of it. I learned SolarWinds IPAM by myself in a POC environment, and not just IPAM but other modules and now I own 6 certifications. You see how easy to use this product is.
We do not integrate IPAM into other systems other than the standard Orion integration. The performance is reasonable, however, we are running all the SolarWinds applications on a very large server.
Until today, I have never needed support to Route53 because the documentation is great. But, I have needed it for other services. And they're near perfect always. Except that they don't have Portuguese support yet and they're sometimes slow to answer (48 hours in non-critical ones, in two tickets). But usually, they're amazing!
I have not contacted customer support and therefore have no experience in this area. I know we have some issues with our VAR support at this time for Orion, but I don't know if the IPAM falls into the same support structure. Perhaps others in the organization may know more regarding the support area.
We purchased our domain names through Networksolutions.com and do rely on their DNS services for basic functionality (SPF hard reject records, etc.), since it was included at no cost; however, for our main domains, we utilize Route 53 because of AWS's high availability, reasonable cost, and capabilities to integrate with EC2 and other security certificate services to make hosting on AWS simple. We also front-end some of our sites with Cloudflare and while it's not as streamlined as using AWS natively, it does a good job.
SolarWinds IP Address Manager was cheaper than both alternatives and far easier to manage. Device42 interface is years behind what Solarwinds offers. It is very outdated; BT Diamond required remote management and we constantly had to message support, it reached a point where it was better not to have the product at all.
We have not experienced any scalability issues with this product. However, SolarWinds needs to allow users to scale horizontally without any license restrictions. For example, we would like to separate Netflow and Orion onto different platforms but are unable to due to license restrictions.
IPAM has saved countless hours of running scripts and gathering data to compile reports to plan re-subnetting globally.
IPAM has reduced helpdesk incidents by immediately spotting bad DNSR and IP conflicts.
IPAM has helped eliminate blocks on projects whereas there is not currently enough address space requiring major changes to accommodate more IP'ed servers, gear, etc.
