# Metricbeat aws module cant collect s3\_dailystorage metrics

**URL:** <https://discuss.elastic.co/t/metricbeat-aws-module-cant-collect-s3-dailystorage-metrics/306512>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [June 7, 2022, 2:16am UTC](https://discuss.elastic.co/t/metricbeat-aws-module-cant-collect-s3-dailystorage-metrics/306512 "2022-06-07T02:16:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![desluk](https://avatars.discourse-cdn.com/v4/letter/d/7ea924/32.png) [@desluk](https://discuss.elastic.co/u/desluk)\
**Post date:** [June 7, 2022, 2:16am UTC](https://discuss.elastic.co/t/metricbeat-aws-module-cant-collect-s3-dailystorage-metrics/306512/1 "2022-06-07T02:16:29Z")

</div>

Hi mate,

I'm trying to collect the ec2, lambda, s3\_dailystorage via the aws module, ec2 and lambda are fine, but no s3 data can be collected. Below is my AWS module config:

```auto
- module: aws
  period: 300s
  regions: 
     - ap-east-1
     - ap-southeast-1
  metricsets: 
    - ec2
  access_key_id: 'access_key'
  secret_access_key: 'secret_key'
- module: aws
  period: 300s
  metricsets:
    - lambda
  access_key_id: 'access_key'
  secret_access_key: secret_key
- module: aws
  period: 86400s
  metricsets:
    - s3_daily_storage
  access_key_id: 'access_key'
  secret_access_key: 'secret_key'

```

My IAM policy is using default managed policy "ViewOnlyAcces" and "ReadOnlyAccess"

Below is the metricbeats log. It looks normal.

```auto
2022-06-07T09:50:39.382+0800	INFO	instance/beat.go:309	Setup Beat: metricbeat; Version: 7.14.1
2022-06-07T09:50:39.383+0800	WARN	[cfgwarn]	tlscommon/config.go:100	DEPRECATED: Treating the CommonName field on X.509 certificates as a host name when no Subject Alternative Names are present is going to be removed. Please update your certificates if needed. Will be removed in version: 8.0.0
2022-06-07T09:50:39.387+0800	INFO	[publisher]	pipeline/module.go:113	Beat name: XXX-YYYY
2022-06-07T09:50:39.541+0800	INFO	instance/beat.go:473	metricbeat start running.
2022-06-07T09:50:39.541+0800	INFO	[monitoring]	log/log.go:118	Starting metrics logging every 30s
2022-06-07T09:50:39.551+0800	WARN	[aws.ec2]	aws/aws.go:101	extra charges on AWS API requests will be generated by this metricset
2022-06-07T09:50:40.843+0800	WARN	[aws.lambda]	aws/aws.go:101	extra charges on AWS API requests will be generated by this metricset
2022-06-07T09:50:44.829+0800	WARN	[aws.s3_daily_storage]	aws/aws.go:101	extra charges on AWS API requests will be generated by this metricset

```

Do you guys have any experience on it?

---

<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:** [July 5, 2022, 4:16am UTC](https://discuss.elastic.co/t/metricbeat-aws-module-cant-collect-s3-dailystorage-metrics/306512/2 "2022-07-05T04:16:47Z")

</div>

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