CloudWatch is the ultimate management and monitoring tool within AWS with a fantastic capability to drill down on data and trends, whilst working to keep your environments safe. We talk about what’s new, how to keep your instances happy and healthy and share Cloud Conformity’s Golden Tips from our team of AWS experts leading the way to the best possible governance, security, and optimization assurance at the infrastructure level. Our mantra: Protect, Detect, Correct.
Amazon CloudWatch is a monitoring and management service providing data and actionable insights to monitor your applications, understand and respond to system-wide performance changes, optimize resource utilization, and get a unified view of operational health. CloudWatch collects monitoring and operational data in the form of logs, metrics, and events, providing you with a unified view of AWS resources, applications and services that run on AWS, and on-premises servers.
CloudWatch News 2018: More Power to You
Extended Metrics for Insights
Understanding that users are wanting to get more out of their data, AWS introduced new features this year to improve the insights you can get out of CloudWatch.
- Using CloudWatch Metric Maths, you can perform calculations across multiple metrics for resource review and analysis without the need for additional scripts.
- For those using AWS SNS, CloudWatch can now monitor how well the service works when using subscription filtering policies giving you the option to ratify the operation and efficiency of those very filters.
- Most recently, AWS have integrated StatsD and collectd into CloudWatch to give you even better visibility of your stats and metrics. By leveraging the custom metrics in the open source solutions, monitoring, analyzing and troubleshooting your applications is made easier within AWS.
Even Further Automation Options
Using CloudWatch alarms and events to even greater effect, AWS has enabled the service with others so further automation helps you to track and manage any changes in your infrastructure.
- You’re able to now track tag changes without the need for continuous API calls and to set up triggers for AWS Lambda events.
- AWS CloudBuild is now set up with CloudWatch alarms so current and past builds can be monitored, efficiently highlighting failed builds and general trends to encourage improved troubleshooting.
- In October, AWS announced additional notification options for subsequent updates for existing GuardDuty findings. The additional intervals of 15mins and 1hr to the default 6hrs undoubtedly provides you greater confidence in the management of any threats to your AWS resources.
Let’s review best practice for efficient monitoring and making the most out of AWS CloudWatch to keep your infrastructure running seamlessly and securely.
A few key questions to ask yourself when setting up and maintaining monitoring of your environments:
- What are your goals for monitoring?
2. How often will you monitor these resources?
3. Who will be performing the tasks?
By getting clear on these questions, you can adopt the best policy for your organization. The beauty of CloudWatch is the ability to automate as much as possible from setting up alarms and notifications to creating events to trigger responsive actions such as alerts monitoring security groups for changes. It already works seamlessly for major AWS services, including S3, IAM and EC2, by offering EC2 instance state-change notifications, which help you to analyze trends so you can work even more productively
Cloud Conformity’s Golden Top Tips
- Before paying for a third party monitoring tool invest a little effort to see what CloudWatch and CloudWatch alarms can do for you. It only takes a few moments to build an app dashboard that shows you your HTTP 400s, 500s and latency, and create some quick thresholds for generating alarms. This is most effective when you have turned on the most appropriate monitoring for your resources.
- You can now build an AWS CloudWatch alarm outside of the AWS console. This allows you to embed an image of your alarms on a web page or wiki and with a bit of configuration, send it to a Slack channel.