Amazon CloudWatch Review

Scalable and stable with an easy setup


What is our primary use case?

We are primarily using the solution to monitor some of the instances that we have on Amazon for our testing development.

How has it helped my organization?

We are able to, on a real-time basis, understand the capacity utilization and the latency aspects, and, to that extent, we can now know the productivity of the tests and if the development team has increased them in any way.

What is most valuable?

The solution works well as part of an overall Amazon ecosystem.

The solution is easy to set up.

The solution gives us very good real-time data.

What needs improvement?

The drill-down aspect on the dashboard of the solution needs improvement. We get a very good high-level overview, but when we drill down, it becomes a little less clear. We have given this feedback to AWS as well and hope they will improve this in the future.

For how long have I used the solution?

I've been using the solution for about three and a half years now.

What do I think about the stability of the solution?

The solution is very stable. We haven't had issues with bugs, glitches, or crashes.

What do I think about the scalability of the solution?

The solution scales quite well.

It's the infrastructure team that is using the solution at our organization. It's a team of about seven or eight people and they are using it to monitor the performance of the cloud instances to address any degradation.

The solution is currently being used in 100% of the Amazon instances that we are leveraging. Unless we increase the number of instances on Amazon, we are not planning to scale this product beyond what we are using. We are already using it to the maximum.

How are customer service and technical support?

Amazon's technical support is a tiered support system. In our case, we have somebody who's available to us and they call us to assist if we need them to.

Which solution did I use previously and why did I switch?

We didn't previously use a different solution. We've only ever used Amazon.

How was the initial setup?

The solution's initial setup was fairly simple and straightforward. 

The deployment took less than a week. Once we started, our first task was to understand the solution and how we could best leverage it for our environment. Once we had that configured, we then started working towards deploying it.

What about the implementation team?

We worked directly with Amazon. We didn't work with an integrator or reseller.

What's my experience with pricing, setup cost, and licensing?

We have monthly licensing costs. The licenses are probably in the vicinity of about $300 - $350/month.

There are no other costs or hidden fees beyond the licensing.

Which other solutions did I evaluate?

We didn't evaluate any other solutions. This is because this was the product that was native to Amazon and so this, we knew, would suit us. There was no need for us to look at another product at that time we set this solution up.

What other advice do I have?

We're not using the latest version of the solution. We might be using the latest version minus one.

I would advise other users that they need to understand the solution and what it is capable of doing. From there, they should build out their use case and try to see if the solution will fit into it. It's a good idea to do a POC.

Unless you do a technical evaluation and a proof of concept, you will not be 100% thorough in your preparations before implementing any kind of solution. 

I'd rate the solution eight out of ten. 

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest