Amazon DevOps Guru Reviews

I have been using Amazon DevOps Guru while working with certain organizations. Some of them were product-based, and some of them were consultants. Based on the requirement of the customer, we would select whether to go with AWS, Azure, or GCP, and then we would design and create the architecture for this. Then we would deploy all the servers required for all different environments, put in the DevOps tools with CI/CD and the monitoring in place, and then hand it over to the customer.

I have worked with integrations of Amazon DevOps Guru with other AWS services.

I purchased Amazon DevOps Guru through the AWS Marketplace.

Predictive metrics in Amazon DevOps Guru help to reduce application downtime.

It is beneficial in terms of tasks that were earlier being done manually and there were no standard operating procedures. Nowadays, things are actually coming under that as it is, so that definitely helps. This gives time to actually think about bigger solutions and problems. These things are now more advanced and AI-driven, so it definitely helps on that front.

Something could be done at least in documentation in Amazon DevOps Guru. It could be better in that area.

When I started maybe 20 years back, technologies and DevOps itself were new, and there were fewer services. Nowadays, if I remember correctly, in 2007-ish, AWS had only five services. Now there are maybe more than 300 or 400 services on AWS. One thing that could be challenging is based on the requirement, which tool to exactly choose if you are a newbie or a beginner. That could definitely be a challenging thing. Another thing is the documentation part. With more complex aspects nowadays, it is challenging to actually develop the architecture and document everything as things are changing.

I have been working with DevOps and cloud for almost 18 years now. I work with AWS, I work with Azure, and I have had my hands on GCP. On the CI/CD part, I have been using Jenkins, Azure DevOps, and a lot of other monitoring tools.

Amazon DevOps Guru is pretty stable most of the time. We have had a couple of issues, but since we are talking to people who have actually built the technologies or who have been part of these technologies, most of the time the solutions are stable.

I do not remember any incident where we basically had to consider scalability. With other tools and services which are available with AWS, scalability has never been an issue.

It depends on the company, to be honest. I have worked with many companies and some of them have one of the reasons people come to the cloud because things are cheaper if you tap on it. But then it can actually go totally uncontrollable if you do not take care of that. Some people have a budget of about $1,000 a month, some have a budget of $10,000 per month. Based on the budget of the company and how big the company is, the answer to that is debatable.

I would say somewhere around seven or eight for technical support from AWS, in my subjective opinion.

Positive

That is based on the budget. If you take the premium package, and in one of the companies, we had taken that, so the response was very good. But if you are a startup company where you do not want to shell any dollar onto support modules, then sometimes it becomes problematic.

The deployment process is pretty straightforward in general. The way I see it, and with so many years of experience, it is pretty straightforward.

The complete name is Amazon DevOps Guru.

I have been working with AWS since 2012, specifically with AWS DevOps.

I am speaking about Amazon Web Services when I mention AWS.

I am into DevOps, so I have been using a lot of tools recently.

For the detection of anomalies, if talking specifically about monitoring, I have been using a lot of tools. Nagios is there, Zabbix was there. But if talking about performance monitoring, New Relic was there, Site24x7 was there. Based on whatever is the requirement, we will deploy those tools.

For incident management, it was mostly done earlier by some scripting tools. We would have the shell script to monitor the system and basically send us an alert, and then based on the budget, the company would decide on tools such as Atlassian or a long time back we had tools such as FileZilla or Bugzilla. But nowadays, with most of the companies that I have worked with in the last maybe nine or 10 years, most of them have been using Confluence. Recently, we added ClickUp as one of the tools. Some of them are also using monday.com. Based on the quorum, the tool was decided and incident management tools do help. We also use tools such as PagerDuty and Opsgenie for incident management.

Of course, you need to choose the right set of tools for the deployment. Whether you are using this for DNS, whether you are using that for a database or simple application servers, you need to decide on what tools or what services you would want to use for those things. Then based on that, you design it and you decide it.

I have not found any negative side to Amazon DevOps Guru. Maybe because of the experience that I have, I would find my way out and find a solution. But I would not say there is any negative side to that. Maybe somebody who has started using that newly could find some negative side, but as of now, all is good.

I started out with AWS in 2007. I started with Azure in 2015 on the cloud side. But if talking about specifically DevOps, I started with DevOps on Azure first before going to AWS. If talking about the cloud journey, AWS has been the first cloud. But if talking about DevOps, because in AWS we were still using scripting, Ansible, Chef in the old days, and Puppet. But if talking about a proper tool from the cloud service provider, then Azure DevOps was the first one which I basically tried. I guess most of the services provided by any of these cloud service providers are the same. It is just a change in the names and the way they actually do things. It is just a personal preference.

My overall rating for Amazon DevOps Guru is eight out of ten.