Amazon Web Services (AWS), established in 2006, is focused on providing essential infrastructure services to businesses globally in the form of cloud computing. The key advantage offered through cloud computing, particularly via AWS, is its capacity to shift fixed infrastructure expenses into flexible costs. Businesses have been able to forgo extensive planning and procurement of servers and other Information Technology (IT) resources, owing to AWS. AWS seeks to provide businesses with prompt and cost-effective access to resources using Amazon's expertise and economies of scale, as and when their business requires. Currently, AWS offers a robust, scalable, economic infrastructure platform on the cloud powering an extensive array of businesses worldwide. It operates across numerous industries with data center locations in various parts of the globe including U.S., Europe, Singapore, and Japan.
Do You Manage Peer Insights at Amazon Web Services (AWS)?
Access Vendor Portal to update and manage your profile.
In our experience, the best thing about CloudWatch is connectivity with their own services. For example, if I need logs for the Lambda, I don't need to attach the event to the service; it comes by default with CloudWatch logs. Then we have the CloudWatch Logs Insights service, which is basically a query for the CloudWatch data. For example, sometimes we have millions of data in our backend server or UI server, so if we need to find the specific logs, then it is very hard to go through all the log groups and all. At the time we used these log insights; it helped us a lot to find it. Another thing is alarms are basically used to give you an alert when your point is hit. This helps us to continue monitoring the performance of our services, and there are many different services as well.
Native integration with multiple aws services which is a great advantage
We love deep AWS integration which allows us to see logs from all our cloud services in the same place. We also like that for alarming and notifications we can use AWS SNS with a wide variety of notification options.
While excellent for starting up, CloudWatch can become expensive when we start adding in the logs, and logs grow, store the logs for long periods of time, and use custom metrics, which can increase our monthly bill. And sometimes the UI for the console can feel very cluttered. It takes time for the new team members to get used to it, and using logs insights also takes time when you are new because of the query syntax. It is not same like simple sql it is hard in the beginning. When you start working continuously you feel more familiar with it
log ingestion and retention cost is high and very limited visualization capabilities.
We don't like how the costs accumulate fast if you need to use detailed monitoring and keep logs for a large period of time. That's why as I said above Cloudwatch is our first line of monitoring and is being used for immediate alerting and as a temp bucket for logs which are then being sucked out into our ELK stack. Dashboards are not the strongest feature of Cloudwatch. For this we have to use other solution.