Metricbeat aws module cant collect s3_dailystorage metrics

Elastic Stack Beats
1

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:

- 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.

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?

2

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