# Metricbeat-credential alternatives

**URL:** <https://discuss.elastic.co/t/metricbeat-credential-alternatives/305255>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [May 20, 2022, 6:16am UTC](https://discuss.elastic.co/t/metricbeat-credential-alternatives/305255 "2022-05-20T06:16:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sadik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sadik/32/95771_2.png) [@sadik](https://discuss.elastic.co/u/sadik)\
**Post date:** [May 20, 2022, 6:16am UTC](https://discuss.elastic.co/t/metricbeat-credential-alternatives/305255/1 "2022-05-20T06:16:53Z")

</div>

```auto
Hi Team,

In "metricbeat.modules:" session we are using the "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY" to estrablish the connection 
from AWS module(metricset:"lambda") to connecting to kubernetes cluster and getting the logs from there.

But here we are facing the issues of "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY" are expired every 90 days and we have manually generated the new "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY" and update the same here. IF we forget to generate the new "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY" on time facing so many connection problems from the end-users.

So, we are looking for other alternatives, so can you please confirm, if is there any possibility we can use instead of "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY" to connect the connecting here?

Thanks in advance!!!

Regards,
Sadik

```

---

<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:** [June 17, 2022, 8:17am UTC](https://discuss.elastic.co/t/metricbeat-credential-alternatives/305255/2 "2022-06-17T08:17:15Z")

</div>

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