Metricbeat AWS module on Kubernetes error

Elastic Stack Beats
,
1

Hello,

We have enabled the AWS module on a metricbeat on Kubernetes. The beat starts, but fails with the error message 2020-08-27T18:50:39.511Z ERROR instance/beat.go:958 Exiting: 1 error: metricset 'aws/ec2' not found.

Is this caused by missing AWS credentials, or is it a beat configuration error? The credentials should be in place, but I not quite sure.

2

Thanks for posting your question here!

What does command ./metricbeat modules list return? Also what does your modules.d/aws.yml look like if this file exists.

3

Hello @Kaiyan_Sheng,
Thanks for helping on this issue. The beat is version 7.8.1. It has the system and the aws modules enabled Enabled: aws system. For the aws module I have tried all metricsets, a few metricsets and only the ec2 metricset. The result is the is the same. The beat stops with an error messages similar to the above. Basically, the metricsets are configured a shown in the beat documentation. The credentials are not set directly in the module configuration, since the devops claims that this is handled implicitly by the roles and privileges the metricbeat is configured with in aws. I belive the credentials or at least the role_arn should be set configured in the module as shown in the beat documentation. What is correct?

4

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