Amazon CloudWatch vs AWS Config

Need advice about which tool to choose?Ask the StackShare community!

Amazon CloudWatch

8.1K
5.3K
+ 1
214
AWS Config

46
78
+ 1
6
Add tool

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.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Amazon CloudWatch
Pros of AWS Config
  • 76
    Monitor aws resources
  • 46
    Zero setup
  • 30
    Detailed Monitoring
  • 23
    Backed by Amazon
  • 19
    Auto Scaling groups
  • 11
    SNS and autoscaling integrations
  • 5
    Burstable instances metrics (t2 cpu credit balance)
  • 3
    HIPAA/PCI/SOC Compliance-friendly
  • 1
    Native tool for AWS so understand AWS out of the box
  • 4
    Backed by Amazon
  • 2
    One stop solution

Sign up to add or upvote prosMake informed product decisions

Cons of Amazon CloudWatch
Cons of AWS Config
  • 1
    Poor Search Capabilities
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    What is Amazon CloudWatch?

    It helps you gain system-wide visibility into resource utilization, application performance, and operational health. It retrieve your monitoring data, view graphs to help take automated action based on the state of your cloud environment.

    What is AWS Config?

    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.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Amazon CloudWatch?
    What companies use AWS Config?
    See which teams inside your own company are using Amazon CloudWatch or AWS Config.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Amazon CloudWatch?
    What tools integrate with AWS Config?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Jul 9 2019 at 7:22PM

    Blue Medora

    +8
    11
    1762
    +23
    12
    6333
    +25
    7
    2810
    What are some alternatives to Amazon CloudWatch and AWS Config?
    Datadog
    Datadog is the leading service for cloud-scale monitoring. It is used by IT, operations, and development teams who build and operate applications that run on dynamic or hybrid cloud infrastructure. Start monitoring in minutes with Datadog!
    Splunk
    It provides the leading platform for Operational Intelligence. Customers use it to search, monitor, analyze and visualize machine data.
    New Relic
    The world’s best software and DevOps teams rely on New Relic to move faster, make better decisions and create best-in-class digital experiences. If you run software, you need to run New Relic. More than 50% of the Fortune 100 do too.
    Prometheus
    Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.
    AWS CloudTrail
    With CloudTrail, you can get a history of AWS API calls for your account, including API calls made via the AWS Management Console, AWS SDKs, command line tools, and higher-level AWS services (such as AWS CloudFormation). The AWS API call history produced by CloudTrail enables security analysis, resource change tracking, and compliance auditing. The recorded information includes the identity of the API caller, the time of the API call, the source IP address of the API caller, the request parameters, and the response elements returned by the AWS service.
    See all alternatives