api_key support for elasticsearch-xpack module in Metricbeat

[jasonyoum]

Describe the enhancement:
api_key support for elasticsearch-xpack module in Metricbeat.

Describe a specific use case for the enhancement or feature:
When customer uses /modules.d/elasticsearch-xpack.yml for enabling their Stack monitoring via Metricbeat, they also want to use api_key instead of username/password. They got 401 Unauthorized error since api_key is not supported yet, and had to go with username/password instead.

[elasticmachine]

Pinging @elastic/stack-monitoring (Stack monitoring)

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[igoristic]

Do you mean doing something like this: https://www.elastic.co/guide/en/beats/filebeat/current/beats-api-keys.html

Also not sure if related, but there's also this: https://www.elastic.co/guide/en/cloud/current/ec-cloud-id.html

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

[bzarbalthazar]

This would be nice to see as the recommendation has been to move away from user/pass. We also have tried using role mappings using PKI but those fail with 401 as well. Any movement would be appreciated on this.

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

[bzarbalthazar]

is this being put on the back burner in lieu of using the elastic-agent now?

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!