Amazon EKS Reviews

I use Amazon EKS for one of my customers when I am an independent contractor. They do video recording for events such as weddings, advertisements, and other occasions. They wanted to stream their content, and I advised them to use Amazon EKS as a good solution so they can easily ingest the raw materials, process it, do all the cuts using specific video software, and then publish it wherever they need.

The ease of implementation and integration was accomplished by writing some small scripts. I implemented workflows for data ingestion, sending it for cuts, and then directing it to the presentation layer. The simplicity of it was key.

The automated patching feature for the Kubernetes clusters provided valuable benefits through ease of maintenance and simplification of maintenance. I don't have to manually monitor or create any additional services for monitoring the patches; it's just there and does the work automatically.

From my perspective, integrating existing applications into a single workflow is beneficial for application development and application integration.

The workflows were straightforward, collecting data from raw recordings from cameras, putting them on cloud storage, ingesting them into video editing software, and going to a CDN for publishing.

About a year and a half ago, the cost was somewhat high. Though I wasn't directly affected as my customer paid for it, they complained about the billing. If they could reduce the price, that would probably attract more customers, especially from this industry, as they are rather small companies with limited budgets for such tooling.

I have been working with Amazon EKS for about a year and a half, with my first notes dating from March 2024.

I escalated a couple of cases to AWS support. I have mixed feelings about this as they were quite helpful, but the response times were quite long. It took them about five business days to get a response to my question, but when they replied, the response was very valuable and helped me.

I didn't notice any crashes, slowness, or performance issues with the Amazon EKS product. My client could have potentially experienced such issues while using it, but they never reported any complaints, so I don't believe there were any issues.

I would rate the tech support around seven or eight on a scale of one to ten.

I worked with container services about a year ago as part of my project at that time. I enjoyed using AKS, but I think its equivalent in AWS is better; it's more mature and easier to implement than AKS on Azure.

The best feature I found in Amazon EKS is ease of implementation. I'm not very knowledgeable about video software and had to learn it quickly for this specific project, and I found it very easy to implement. It probably took me a couple of hours to really understand it and learn how to use videos, and it was probably the easiest of all the solutions that I tried.

I use the DevOps server as software as a service on Azure. I didn't need to set any server for that; it was just there. I added it to my dashboard and started using it.

In terms of cost savings, time savings, and efficiency improvements, I've definitely seen returns on investment. Considering my rate and the couple of hours spent, rough calculations show around 30% return on investment.

The majority of my time setup cost was very affordable, taking just two hours. It was easy as I didn't have to worry about setting all the infrastructure underneath, just using what's there. This saved my time, allowing me to complete the project within several hours instead of days or weeks.

When I evaluated several solutions, Amazon EKS looked more intuitive to learn. I was prototyping for two hours each, and with Amazon EKS, I had this raw prototype running after around two hours. With other services, after two or three hours, I was still in the middle of my work with no visible effect, so that was the benefit.

I am working with a set of tools within the Azure toolbox. Azure is a huge collection of services with over 100 of them. I use virtual machines, Azure Functions for serverless processing, especially for creating APIs that do automated tasks. Additionally, I use SQL Server database and infrastructure as code, creating using Terraform, creating virtual private networks, setting up firewall rules to increase the security of my customer's solution.

I give Amazon EKS a rating of 8 out of 10.

Amazon Web Services (AWS)

I usually work with AWS tools focused on infrastructure deployments, onboarding new customers to the cloud, and offering the best practices across infrastructure, networking, security, monitoring, and availability, discussing high availability solutions and implementing the best practices over these. That's mainly my scope. For the development part, when it comes to services such as functions, Lambda functions and X-Ray and development services, I actually interfere with them in the deployment part and not for the configuration or the development part.

I've built a tool that can manage all these resources, whether it's on Microsoft Azure or Amazon Web Services or Oracle itself. This tool is efficient when it comes to assessments, assessing the environments for customers, getting the best security practices and measurements across the environment the customer has, having a cost optimization component that can be used to optimize the cloud environment. It covers automated deployments that you use with a user interface, so you don't have to write any code while deploying complex scenarios.

Regarding my experience with Amazon EKS, I have a complete solution for deployment as well. The tool is really powerful and can be used to do various things. I'm involved in the infrastructure, networking, and deployment part, so deploying these resources is one of my daily responsibilities. I use this tool to deploy all of these.

The deployment process for Amazon EKS is straightforward; you don't have to do anything basically. You just have to get the right image and the normal operation for Amazon EKS.

The best features of Amazon EKS involve the orchestration, which may be the concerning part of each customer when it comes to Amazon EKS especially. The automation part, the deployment and monitoring part, the security as well, having the connectivity going private or public, or using Kubelet are various aspects that users should be aware of, providing good experience while discussing these options with customers.

The integration capabilities of Amazon EKS seem fine, but it can be challenging using AWS services compared to other cloud providers, for example, Microsoft Azure. From using both platforms, Microsoft Azure offers more simplicity while doing complex deployments. AWS offers the same solutions; however, it seems more complicated when it comes to independent resources, where you need to establish dependencies before doing the actual resource deployment. This part needs an automation layer that already exists with the Microsoft Azure portal, which facilitates everything for the user experience.

I don't see much room for improvement for Amazon EKS; the Kubernetes technology is the same across all cloud providers. Most customers focus on the main common features they will use, such as the monitoring or the orchestration part, which is their main concern when it comes to this service specifically.

I have experience using Amazon EKS for approximately six years.

Regarding technical support from Amazon, I never personally experienced it, but the team I'm handling has faced their support, and they indicated they're quite good, but not on the first level part.

Positive

I have definitely seen an ROI with Amazon EKS. I developed a tool for cost optimization that can cover all of these, even with better approaches than the cloud itself. The tool I developed uses the native AWS recommendations, so ROIs and any saving plans that can be offered are included within the cost optimization. However, we've added our experience component upon using these resources as well.

For example, AWS will never tell you that you have to delete a virtual machine or an EC2 instance. However, our report can detect the stopped instances and provide a recommendation for the customer that for cost saving, they can use a backup or snapshot for this machine, and delete it. If they need to restore it, they can do that, or they may have to remove it if they're not using it.

In terms of pricing for Amazon EKS, I think it's quite reasonable. If we compare the cost to other providers, with providers such as Oracle, it will be much higher in cost. When comparing it to Microsoft Azure, it seems similar, with some variations. On a scale of one to ten, I rate Amazon EKS a seven out of ten.

Amazon Web Services (AWS)

My main use case for Amazon EKS is for implementation and sustainable services and microservice application on a critical structure and services deployment.

On our application, we have more than 20 services and microservices such as authentication, login, account management, a notification service, and a billing service, which all work together to structure a heavy, useful application.

The best features Amazon EKS offers are scalability and deployment control, the ingress configuration regarding path pattern and host header to get all the services and microservices, and the HPA configuration.

The biggest difference, or the most important aspect to me, is the scalability, because you can easily scale any service or microservice to handle security during high changes in connection flow, and it is useful for the application and helps day-to-day by giving us reliability and stability so we can perform all maintenance and deployment of our system.

Reliability is a very important thing. Security and operational consistency are very important aspects, and the flexibility offered in node management and network options is also valuable. Amazon EKS is a service that is reliable and scalable, and it gives us a solid and dependable solution.

I think sometimes the documentation is not so clear and not so fast to provide more in-depth instruction and examples of bigger and critical implementations, so some difficulties for us sometimes take a lot of time to understand, test, and to put into production with security and guarantees.

I have been using Amazon EKS for almost five years now.

I advise doing a POC first and getting all the details, testing, and having a very good alignment between DevOps and development departments, and prepare all the CDN and how the connections get into your cluster, and how you configure your ingress and how to prepare every service or microservice to receive that with secure and optimized code, process, and communication with other resources. I would rate this product an 8.

Private Cloud

Amazon Web Services (AWS)

I have been working in my current field since I work in the cloud, and I worked for AWS and for Amazon EKS because all of my customers are using Amazon EKS or application container solutions.

My use cases for Amazon EKS involve working for an AWS partner, one of the biggest in LATAM, where we have many customers or clients around the world with different solutions. I have a client that had many applications in Amazon EKS, and I had the full administration of the cluster. I manage not only networking, pods, or resources but also security, monitoring, the billing for the expenses, access to the cluster, and to the AWS account. I think that is a big field that I can handle within Amazon EKS.

What I appreciate most about Amazon EKS is that I use tools such as Datadog for monitoring and reporting, and if I have a problem with the cost, I use Prometheus, Grafana, and Loki, as this Prometheus package is cheaper than Datadog. I use Helm to install packages or applications, making it easier and secure to install, uninstall, or update them. I also use Argo CD for CI/CD workflows. In general, these are the main package solutions that I use for Amazon EKS.

Regarding the downsides of Amazon EKS, I remember a case where I used a network add-on different from what is provided by AWS because the pods request one IP address for each pod. The solution had many pods, and the blocks in the VPC were limited. I didn't have enough addresses to assign to the pods, and I had to change the add-on to handle the IP address using another third-party solution not from AWS. This was one of the first challenges I encountered with Amazon EKS.

Since then, AWS still hasn't fixed this issue or given me an opportunity to use the IPs that I needed.

Basically, the problem was that we did not have enough IP addresses for the pods, and we had to change the network add-on in Amazon EKS.

I have been using Amazon EKS in my career for three and a half years since I worked in the cloud.

It took me approximately one month to learn how to use Amazon EKS. The tricky part was implementing Amazon EKS cluster completely from Terraform, as creating all of the resources is challenging. If you create the cluster from the AWS console, many resources are created behind the scenes, but in Terraform, you must create each resource one by one, which was quite difficult. Overall, it took about one month.

Regarding stability, I have not experienced any lagging, crashing, downtime, or instability with Amazon EKS. I think that Amazon EKS, and Kubernetes in general, is stable. I have had problems with billing because it's expensive, but not with stability.

When it comes to scalability, I use Carpenter with Amazon EKS because it is a tool that offers significant granularity for configuration, and it works really well and fast. The inherent scalability of Kubernetes is not the best for me based on resources, but Carpenter works really nicely.

I have contacted the technical support of Amazon EKS when I had issues with the IP addresses, and they helped me solve it by installing another network add-on. On a scale from 1 to 10, I would give the support of Amazon EKS a nine because it was nice and fast.

Positive

I have used a direct alternative to Amazon EKS, which is ECS in AWS. I have many clients using ECS, Elastic Container Service, which is the native service for containers in AWS. It's not the same as Amazon EKS; it's another orchestrator, but it works fine when your application is not big.

The initial deployment with Amazon EKS was easy, but I remember that my first deployment was done with a YAML file, just using kubectl. I used kubectl run and the YAML file, and after that, I learned about Argo CD, which made the process much easier.

Amazon EKS does require maintenance on my end. Last year, Kubernetes had many updates, which was a difficult task. This is why I use Helm to install all of the applications in the cluster. If the application is built for you, you can create the Helm chart for this application and install it using this tool. I think that is the best option when you need to update the cluster. I know that AWS now offers many new applications add-ons included in the console, making it easier, but I still think that maintenance is one of the most complicated aspects of the cluster.

On a scale of 1-10, I rate Amazon EKS a nine.

Public Cloud

Amazon Web Services (AWS)

The main reasons for using Amazon EKS in our use were third-party solutions that were distributed as Helm charts. We were using Rancher to manage multi-cloud deployment for unification. We are also using it for evaluation purposes, building customer pilots and prototypes. Sometimes it is easy to make the build chain run through and come out as images and deploy them into Kubernetes.

It completely depends on use case. If you have got a very dynamic or a requirement to scale very fast with nodes, then Amazon EKS is a very good choice because you have got that reach and the ability to scale quickly. But if you have got a fairly static load, it becomes quite expensive quite quickly. They are expensive CPU cycles.

The main benefit of Amazon EKS is its rapid deployment. The fact that we can deploy it very quickly with infrastructure as code and then tear it down again when we are finished.

There is no real advantage to us from Amazon EKS because the advantage is the fact that we have a unified management product so we can deploy concurrently into multiple clouds and on-prem out of one pane of glass. That is the key thing there. As far as the development and presentation, sometimes it is easy just to load it up through kube control, sometimes you put it through a GUI control in front.

We have not been using it from the point of the application using the IAM. We have been using it because quite often our customers are tied back to usually Entra ID and things like that.

The only concerns I had with Amazon EKS were related to cost, the usual problem you have with cloud. It is fine if you can exploit it for dynamic loads, bring it up, get rid of it again. That is where its strength is. You pay for that premium, but as far as running the thing under constant load, it is a very expensive way of deploying.

In the early days, there were a couple of vulnerabilities exploited from the single control plane per region. So there is nothing stopping me deploying multi-region, and that means multiple control planes. So I could deal with that, the infrastructure handled the criticality. The only thing that I could possibly run into a problem with, which I have not had to at this point, but architecturally, is with regulated technologies, banks, that sort of stuff where you cannot be single provider sensitive.

We have been dealing with it from the beginning almost, since 2019.

Only in the past I think it had issues. The fact that regions only had a single control plane left a little bit of vulnerability in there, certainly in the early days, but I do not think that matters now. They seem to have solved that.

I had no problem. It was stable. Very stable.

It was very easy to scale.

The current stuff I am working with has been Kubernetes and building out operational software using Kubernetes. I was actually reviewing Nutanix as an option for some of the stuff I was building out.

Mainly on-prem, we are doing production work with a number of customers. We support them, we run an operational arm as well. I have been involved in platforming on Kubernetes, but we happily support any variant. We are cloud agnostic. So these distributions, we would use Amazon EKS or AKS, but not for long.

The driver in Rancher, as long as I do not have anything extremely different or complex, works completely the same whether I am driving the application onto Amazon EKS or onto a local on-prem.

We have not been using the automated patching. If we were in anger, we do not run the stuff long enough in Amazon EKS at the moment. Really, it is just up in demo and then torn down again. A lot of the stuff is being driven from other automation anyway, more infrastructure as code stuff. So that actually just gets driven completely in there.

I think that Amazon, every other provider, is adapting to the changes in the market now because the major cloud benefits are now fully saturated. Nobody else is going in for those benefits. They are starting to hit the reality of regulated technologies that are high value cannot be under a single provider. So a single cloud provider is not sufficient to support critical industry anymore. You have to have either multiple cloud or hybrid just to meet regulation in the future. So that constrains some of the flexibility. But the clouds are all working towards more on-prem extension, that sort of thing to make it more feasible.

I would rate Amazon EKS a six out of ten. I have a particular penchant for not actually overscoring anymore because of the way that people use this stuff. In other words, I consider adequate doing what it says they claim it to do. So that is a five or a six as they did what they said they would do. There is nothing wrong with that. It is what we agreed. I paid for it, they delivered it. I am satisfied.

Hybrid Cloud

Amazon Web Services (AWS)

I describe my use cases as being for web applications and for API applications.

Simplified application deployments and infrastructure management

What I find best about Amazon EKS is its simplicity and that I don't need to care about control plane. IAM authentication has been a great feature, and with the latest changes, we don't need AWS ConfigMap.

The benefits I have seen from using it include simplified Terraform code, and the fact that we don't need to configure OIDC anymore. Additionally, we don't need to manage ConfigMap.

I don't know how Amazon EKS can be improved; it's ideal already.

I have been using it for five years, since 2020.

I don't remember any issues at all regarding stability.

The scalability is great with Carpenter; however, I don't know about the scalability of control plane, but worker nodes scalability with Carpenter is great.

I have used their support team from Amazon a few times, and it was good, as I remember.

Positive

I did not previously use a different solution.

The initial setup was not complex.

The pricing is cheap, around two USD per day for one cluster, and I think it's a good price.

AWS ECS

I have used Amazon EKS integration with IAM.

I can't remember any challenges while using it, maybe in past years, but not now.

On a scale of 1 to 10, I would give Amazon EKS a rating of 9.

I would definitely recommend it to other people.

Public Cloud

Amazon Web Services (AWS)

I am using Amazon EKS as an integrator.

Regarding Amazon EKS integration with IAM, I do not use it.

To use Amazon EKS as a cloud provider and as a Kubernetes cluster managed by a cloud provider, it offers more benefits because you don't have to configure the cluster on your own. You can use the default configuration and just set the right networking space, set the subnet, and a few other things, but you don't have to raise up or configure your own cluster.

Self-healing nodes help to minimize administrative burdens in the organization. It helps to keep the nodes up and running. Then you can use other solutions to minimize costs or to keep the nodes running most of the time.

You can use Amazon EKS to raise up clusters and deploy applications in the cluster. The cluster is managed by Amazon, so you don't have to configure it. You can use the basic configuration of Amazon, and you don't have to interact with etcd or with the Kubernetes most inner parts. It's more simple to use.

Amazon EKS can give you more flexibility to configure on their own. In general, it's a good product. There are many different products that can fit the needs of the user or the customer in every part of AWS. In Amazon EKS, they can give a class that can be more configurable from the user or expert user rather than just using the default EKS.

Amazon EKS support for AWS tools integration has an impact on application development and management because everything is deployed on the cluster. You have to debug the various pods in Kubernetes. There isn't a direct impact, but there is an impact because everything you deploy through the pipelines goes to the cluster and there you have to integrate the cycle.

The main problem or area for improvement is flexibility in configuration. This is the only concerning part and nothing apart from this.

I have been using solutions similar to Amazon EKS from other vendors. I used GKE from Google, the cluster of Azure, and I also used KMinikube. Of course, it's not the same thing, but in general, it can be compared. For testing, K3s are just different distributions. In general, I have used other cloud providers.

It's quite easy to install Amazon EKS.

In Amazon EKS, I see it as a stable product. I don't see any particular issues in terms of nodes or performance.

I believe Amazon EKS is scalable.

I have never used the technical support from AWS.

Neutral

I see return on investment with Amazon EKS. You can save in terms of time because you can raise up a cluster or more nodes, and you can raise up the storage of the particular node in a few minutes. You don't have to take care of managing the machines directly. There is significant time-saving. You don't have to take care of the rack system because AWS has a team that works that part. You have just to pay. In terms of price saving and money saving, it depends on everything, but in general, you're going to save money.

In general, the price of Amazon EKS is expensive, but it depends a lot on the user knowledge of the tool and how we can manage the cost, which solution offers better, which solutions they can use to reduce the cost. For example, the different VM types, the Preemptible VMs or the Preemptible nodes, or you can pay one time for the use, you can reserve the machines. There are many different ways to reduce the cost.

I see big differences between Amazon EKS and GKE. The way you install the cluster is different. In GKE, when you install the cluster, it raises the nodes for you. In AWS, you can install the cluster and then you have to raise up the node using Auto Scaling Group or whatever. It's more integrated maybe. Also in terms of documentation, Google is different from Amazon.

Regarding the automated patching feature for Kubernetes clusters in Amazon EKS, I don't know any patching feature.

On a scale from one to ten, I rate Amazon EKS an eight.

Public Cloud

Amazon Web Services (AWS)

We are migrating our services into container services. We build websites and all of our products' backends are based on Amazon EKS.

The simplicity and management portal make it a neat solution. You don't have to fiddle around with too many open source tools, as it's just a comprehensive solution.

We use the pipeline, which is critical for us to deploy automatically. This eliminates manual intervention, which is really helpful.

We initially had some issues getting the logging out of it, because what they're providing into CloudTrail is what we get. If we wanted to go in-depth, we had to deploy third-party tools. We did try the sidecar way of getting the logs. Ideally, if the platform was able to provide those kinds of valuable logs, that would be beneficial. Adding enhanced logging capabilities would be a nice improvement.

We have been using the solution for three plus years.

Time to value is good with fast deployment and very good documentation that is really helpful.

I don't personally deal with the costing part, but I think it's a fair amount. That's the only reason we're using it continuously, as otherwise we would have moved somewhere else.

The implementation was done in-house.

On a scale of 1-10, I rate this solution a 9.

Public Cloud

Amazon Web Services (AWS)

My main use case for Amazon EKS is to host one of my AI agents which I built recently in my company. I use Amazon EKS to host my AI agent, which is a sprint report agent that fetches the company's data from Jira and prepares a sprint report for the complete team. The agent runs on Amazon EKS for high availability and reliability, hosted on nodes, and it is running on a GPT OS's model in the back end.

I have designed this agent for high availability on Amazon EKS because if I hosted it on any other platform, there would be chances of downtime. I have set it up in such a way that if there is any downtime, a new node is already up and running so that my use case is not affected and the users can use it seamlessly without any issues.

The best features Amazon EKS offers in my experience are its reliability and high availability, and also the support that AWS provides. The reliability and high availability have helped me specifically because there were some configuration issues at my end for the agent, which caused it to go down repeatedly. Due to the high availability features, every time a node downscaled, a new node was automatically scaled up, ensuring that the AI agent was up. I was able to check the logs and correct the issues accurately thanks to that high availability. Also, AWS support is very helpful; whenever I face issues regarding costing or anything else, I just create a ticket and they assist me in resolving the issues.

Amazon EKS has positively impacted my organization by improving the efficiency and working capacity of my team. It improved efficiency and working capacity because, based on how Amazon EKS works, we are more calm regarding functionality. The reliability allows us to focus on many other tasks, as the infrastructure is maintained by Amazon EKS; therefore, we can divert our attention to other tasks and perform well there as well.

Functionality-wise, Amazon EKS is acceptable, but navigation-wise, it could be improved in the AWS console; it could be more interactive and more intuitive for new users. Also, the pricing can be reviewed as it is sometimes a bit pricey, particularly regarding the extended support when new version upgrades occur that we cannot implement directly due to production workloads, as clusters running on extended support cost six times more, which is something that could be reduced.

I believe documentation could be improved on the AWS website so a new user who is starting with Amazon EKS could work much better with it.

I have been working in my current field for three years.

In my experience, Amazon EKS is stable.

The scalability of Amazon EKS is good.

The customer support of Amazon EKS is good. I would rate the customer support on a scale of one to ten as a seven.

Positive

I have seen a return on investment because the reliability has helped me save time; I can rely on Amazon EKS's reliability and then divert my attention to other tasks, so it has definitely saved my time. I estimate that my team and I save roughly one to one and a half hours a day since using Amazon EKS.

Regarding pricing, setup cost, and licensing, the pricing for the cluster part is a bit higher; the setup cost is acceptable, but the licensing part regarding extended support is also a bit pricey, which I think can be handled or reduced.

Amazon EKS is a good product; if you are starting with Kubernetes, it is a good choice, but the pricing is a bit substantial, so you should review that. Also, regarding the support, there are sometimes cases where you need to upgrade your AWS plans for particular support, which can also be a bit pricey. I would rate this product a seven overall.

Private Cloud

Amazon Web Services (AWS)

We are going to be using Lambda on the AWS Stack. We are migrating all our on-premises applications to AWS.

Eggplant is going to be on the AWS platform soon. We are using Lambda functions and CloudWatch for monitoring. We are also using Elasticsearch and ELK.

After we move all the applications to the cloud, we're going to move them into Amazon EKS as containers for easy management. It would be the same as how we are using EC2 instances, but in this case, we're going to move all applications to run on containers, Amazon EKS containers.

We use it for common file sharing across applications. I'm not really sure about all aspects as I didn't use it much. We just set it up to make sure all applications can read. The main capability is allowing different applications to access the same file or resources at the same time, providing collaboration capabilities.

The whole platform is easy because once you set it up, it's easy to onboard applications. It's easy to troubleshoot, run multiple clustering, log management, and perform troubleshooting. You can also install other applications, third-party applications, integration, and all that.

It helps with having dedicated nodes for certain functions. If you want to segregate the work instead of using all the nodes, you're able to align and assign which node processes specific applications, jobs, pods, or runs certain pods.

It reduces the deployment time, setup time, configuration time, and is cost-effective. It's very highly scalable.

The main challenge is at the beginning when you're still learning how to set up. The initial setup and knowing how to do it the first time can be challenging.

We had some challenges with the network pods. There were several pods that we had to try plugins for network, and the load balancing for the application we were deploying was quite difficult to manage.

The documentation should be easier to understand for beginners. It needs to be straightforward and easily grouped together because information tends to be scattered.

Some features required a lot of command line changes, especially setting up ingress and load balancers. If there could be a way to do that on a GUI, that would be easier. Having more configuration options on the UI, especially for setting up load balancers and ingress controllers, would be beneficial.

We have been using the solution for three months.

Currently, we haven't really automated the deployment. We are using Jenkins for our work.

Microsoft tools are being used in the bank.

We haven't experienced any scalability issues.

The support is quite friendly and very helpful. The Amazon support is very helpful and very responsive.

Positive

The main challenge is at the beginning when you're still learning how to set up. The setup and knowing how to do it the first time can be challenging.

I can recommend using it to save costs and for faster deployment, better performance, security, and easy clustering. It's easy to set up, manage, and monitor because when it goes down, it's easy to identify issues. Troubleshooting is straightforward, unlike other applications where you have to do a lot of digging to find the root cause. With this solution, you can see problems directly on your dashboards.

Public Cloud

Amazon Web Services (AWS)