# EC2 system metrics v/s AWS metrics

**URL:** <https://discuss.elastic.co/t/ec2-system-metrics-v-s-aws-metrics/270598>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [April 19, 2021, 2:34pm UTC](https://discuss.elastic.co/t/ec2-system-metrics-v-s-aws-metrics/270598 "2021-04-19T14:34:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![maheshe](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@maheshe](https://discuss.elastic.co/u/maheshe)\
**Post date:** [April 19, 2021, 2:34pm UTC](https://discuss.elastic.co/t/ec2-system-metrics-v-s-aws-metrics/270598/1 "2021-04-19T14:34:43Z")

</div>

Using Elastic 7.9 version with 7.9 beats (EFK self managed). Monitoring AWS-EC2 instances  
Question:

- Can I just use System Module using Metric beats or
- AWS EC2 module is required

Can you please suggest/comment what module is best pros/cons

Metricbeat.yml for reference below

```auto
metricbeat.config.modules:
  # Glob pattern for configuration loading
  path: /etc/metricbeat/modules.d/*.yml
  # Set to true to enable config reloading
  reload.enabled: false
  # Period on which files under path should be checked for changes
  #reload.period: 10s
metricbeat.modules:
- module: aws
  period: 300s
  metricsets:
    - ec2
  access_key_id: ' ***************'
  secret_access_key: ' *******************'
  enabled: true
#- module: system
# metricsets:
# - cpu # CPU usage
    # - load # CPU load averages
# - memory # Memory usage
# - network # Network IO
# - process # Per process metrics
# - process_summary # Process summary
# - uptime # System Uptime
# - socket_summary # Socket summary
    # - core # Per CPU core usage
    # - diskio # Disk IO
    # - filesystem # File system usage for each mountpoint
    # - fsstat # File system summary metrics
    # - raid # Raid
    # - socket # Sockets and connection info (linux only)
    # - service # systemd service information
# enabled: true
# period: 10s
# processes: ['.*']

  # Configure the metric types that are included by these metricsets.
  cpu.metrics: ["percentages","normalized_percentages"] # The other available option is ticks.
  # core.metrics: ["percentages"] # The other available option is ticks.
output.logstash:
 # The FluentD hosts
 hosts: ["dev-hr-fd.mycompany.in:5044"]

```

---

<div class="post-metadata">

**Author:** ![maheshe](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@maheshe](https://discuss.elastic.co/u/maheshe)\
**Post date:** [April 29, 2021, 5:06pm UTC](https://discuss.elastic.co/t/ec2-system-metrics-v-s-aws-metrics/270598/2 "2021-04-29T17:06:49Z")

</div>

I ended up using SYSTEM metrics with COU, Memory metricsets. It also gives the awsinstance Ids.  
Still unsure what additional details the AWS metrics give

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 27, 2021, 7:07pm UTC](https://discuss.elastic.co/t/ec2-system-metrics-v-s-aws-metrics/270598/3 "2021-05-27T19:07:34Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.