# Metricbeat is getting failed when we enable aws metricbeat moulde

**URL:** <https://discuss.elastic.co/t/metricbeat-is-getting-failed-when-we-enable-aws-metricbeat-moulde/315434>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [September 29, 2022, 7:46am UTC](https://discuss.elastic.co/t/metricbeat-is-getting-failed-when-we-enable-aws-metricbeat-moulde/315434 "2022-09-29T07:46:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![samadhan](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@samadhan](https://discuss.elastic.co/u/samadhan)\
**Post date:** [September 29, 2022, 7:46am UTC](https://discuss.elastic.co/t/metricbeat-is-getting-failed-when-we-enable-aws-metricbeat-moulde/315434/1 "2022-09-29T07:46:20Z")

</div>

Hi Team,

We have installed ELK monitoring with following beats version  
metricbeat version 7.9.0 (amd64), libbeat 7.9.0 [b2ee705fc4a59c023136c046803b56bc82a16c8d built 2020-08-11 19:30:31 +0000 UTC]

# packetbeat version

packetbeat version 7.9.0 (amd64), libbeat 7.9.0 [b2ee705fc4a59c023136c046803b56bc82a16c8d built 2020-08-11 19:37:31 +0000 UTC]

heartbeat version  
heartbeat version 7.9.0 (amd64), libbeat 7.9.0 [b2ee705fc4a59c023136c046803b56bc82a16c8d built 2020-08-11 19:19:43 +0000 UTC]

but whenever we are enabling the aws module in metricbeat and restarting metricbeat service its getting failed with error.

2022-09-29T07:36:36.242Z INFO [monitoring] log/log.go:131 Stopping metrics logging.  
2022-09-29T07:36:36.242Z INFO instance/beat.go:456 metricbeat stopped.  
2022-09-29T07:36:36.244Z ERROR instance/beat.go:951 Exiting: 1 error: metricset 'aws/cloudwatch' not found.

sharing aws.yml here

```auto
[root@ip-10-.... modules.d]# cat aws.yml
# Module: aws
# Docs: https://www.elastic.co/guide/en/beats/metricbeat/8.4/metricbeat-module-aws.html

- module: aws
  period: 5m
  metricsets:
    - cloudwatch
  metrics:
    - namespace: AWS/EC2
    - namespace: AWS/ElasticMapReduce
      #name: ["CPUUtilization", "DiskWriteOps"]
      resource_type: ec2:instance
      #dimensions:
      # - name: InstanceId
      # value: i-0686946e22cf9494a
      #statistic: ["Average", "Maximum"]
- module: aws
  period: 5m
  metricsets:
    - ec2
- module: aws
  period: 24h
  metricsets:
    - s3_daily_storage
- module: aws
  period: 1m
  latency: 5m
  metricsets:
    - s3_request
[root@ip-10-.... modules.d]#

```

Could you please help here to get working aws.yml here with existing version of metricbeat.

---

<div class="post-metadata">

**Author:** ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)\
**Post date:** [October 4, 2022, 6:56am UTC](https://discuss.elastic.co/t/metricbeat-is-getting-failed-when-we-enable-aws-metricbeat-moulde/315434/2 "2022-10-04T06:56:36Z")

</div>

Hey, could you try to upgrade to 7.17?

@Kaiyan_Sheng does this issue looks familiar to you?

---

<div class="post-metadata">

**Author:** ![Kaiyan\_Sheng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaiyan_sheng/32/38247_2.png) [@Kaiyan\_Sheng](https://discuss.elastic.co/u/Kaiyan_Sheng)\
**Post date:** [October 4, 2022, 3:07pm UTC](https://discuss.elastic.co/t/metricbeat-is-getting-failed-when-we-enable-aws-metricbeat-moulde/315434/3 "2022-10-04T15:07:32Z")

</div>

Could you maybe try a sub set of your config in aws.yml please? The error message looks like a config issue.

> [@samadhan](#):
>
> ```auto
> - module: aws
> period: 5m
> metricsets:
> - cloudwatch
> metrics:
> - namespace: AWS/EC2
> 
> ```

---

<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:** [November 1, 2022, 3:07pm UTC](https://discuss.elastic.co/t/metricbeat-is-getting-failed-when-we-enable-aws-metricbeat-moulde/315434/4 "2022-11-01T15:07:38Z")

</div>

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