Amazon CloudWatch vs AWS Config: What are the differences?
Developers describe Amazon CloudWatch as "Monitor AWS resources and custom metrics generated by your applications and services". With Amazon CloudWatch, you gain system-wide visibility into resource utilization, application performance, and operational health. Programmatically retrieve your monitoring data, view graphs, and set alarms to help you troubleshoot, spot trends, and take automated action based on the state of your cloud environment. On the other hand, AWS Config is detailed as "Config gives you a detailed inventory of your AWS resources and their current configuration, and continuously records configuration changes". AWS Config is a fully managed service that provides you with an AWS resource inventory, configuration history, and configuration change notifications to enable security and governance. With AWS Config you can discover existing AWS resources, export a complete inventory of your AWS resources with all configuration details, and determine how a resource was configured at any point in time. These capabilities enable compliance auditing, security analysis, resource change tracking, and troubleshooting.
Amazon CloudWatch and AWS Config can be categorized as "Cloud Monitoring" tools.
Some of the features offered by Amazon CloudWatch are:
- Basic Monitoring for Amazon EC2 instances: ten pre-selected metrics at five-minute frequency, free of charge.
- Detailed Monitoring for Amazon EC2 instances: seven pre-selected metrics at one-minute frequency, for an additional charge.
- Amazon EBS volumes: eight pre-selected metrics at five-minute frequency, free of charge.
On the other hand, AWS Config provides the following key features:
- Configuration Visibility
- Fully Managed
- Easy to get started
"Monitor aws resources" is the primary reason why developers consider Amazon CloudWatch over the competitors, whereas "Backed by Amazon" was stated as the key factor in picking AWS Config.
According to the StackShare community, Amazon CloudWatch has a broader approval, being mentioned in 707 company stacks & 321 developers stacks; compared to AWS Config, which is listed in 3 company stacks and 6 developer stacks.
What is Amazon CloudWatch?
What is AWS Config?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon CloudWatch?
What are the cons of using AWS Config?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Config?
Sign up to get full access to all the tool integrationsMake informed product decisions
If you have a single server, checking log files is as easy as SSHing to it and viewing logs. When you move to the container world, with many servers, you need a place to aggregate and search through all of your logs. CloudWatch provides us with this and it was trivial to setup.
CloudWatch is “on by default” in Amazon. And by just configuring a few alarms you can have a near-zero-cost monitoring service of your own.
- Collect metrics for Grafana.
- Alerts for AutoScale.
- Centralized-logging: rds, ec2, app logs with CloudWatch Log
CloudWatch is used to monitor various aspects of our production infrastructure deployed at Amazon.