Feature request: AWS Secrets Manager for storing database connection credentials

[lekspyl]

Hello!

I was looking for ways to set up a database connection in the self-hosted Hoop installation without saving credentials in Hoop's Postgres DB, but unfortunately it seems that it is the only option, which is pretty risky given that credentials are only base64-encoded.

I've stumbled upon the Secrets Manager configuration article, but looks like the information outlined there can only be applied to exec/one-off commands.

Is there a way to securely store credentials for databases in a self-hosted Hoop DB or, even better – fetch the credentials from a secret provider, such as AWS Secrets Manager/Vault?

Thank you for your work!

[sandromello]

Hey @lekspyl ,
The secrets manager configuration support AWS Secrets Manager and HashiCorp Vault. It works for any type of connection.
The exec command are just examples in the documentation.

[lekspyl]

@sandromello thank you for the reply! I was able to configure the connection using the same approach that's listed in the docs for the exec command.
It's worth noting that as of v1.35.22 there is no support for referencing cross-account secrets – I plan to work this around by deploying an agent in each environment.

[sandromello]

I'm glad to know it worked out for you.
Indeed, referencing cross account secrets it's not supported at this moment. Thank your for sharing it.