# Mongodb/Postgres etc modules and password management

**URL:** <https://discuss.elastic.co/t/mongodb-postgres-etc-modules-and-password-management/108336>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [November 20, 2017, 8:33am UTC](https://discuss.elastic.co/t/mongodb-postgres-etc-modules-and-password-management/108336 "2017-11-20T08:33:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![amit\_oren](https://avatars.discourse-cdn.com/v4/letter/a/f05b48/32.png) [@amit\_oren](https://discuss.elastic.co/u/amit_oren)\
**Post date:** [November 20, 2017, 8:33am UTC](https://discuss.elastic.co/t/mongodb-postgres-etc-modules-and-password-management/108336/1 "2017-11-20T08:33:32Z")

</div>

Hello,

I was wondering what are the best practices for password management of these modules and git.  
i don't want to save these as plaintext in github - that's a very bad practice. Is there any way to have them as secrets, etc?

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [November 21, 2017, 10:49pm UTC](https://discuss.elastic.co/t/mongodb-postgres-etc-modules-and-password-management/108336/2 "2017-11-21T22:49:49Z")

</div>

One option here is using environment variables if that is an option security wise for you.

It seems you are creating a config template which is then deployed later. How does that deployment work? Which tool do you use?

---

<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:** [December 19, 2017, 10:50pm UTC](https://discuss.elastic.co/t/mongodb-postgres-etc-modules-and-password-management/108336/3 "2017-12-19T22:50:11Z")

</div>

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