Does vault database secret engine is best suitable for applications or users including both dynamic and static

Does vault database secret engine is best suitable for applications or users including both dynamic and static

Hi @sarathpentapati2001 ,

This is very much a “it depends” - both users and apps can use the database secrets engine, but from the app perspective will be dependent on how the app operates with the database.

For example, in the past I have supported applications that required a restart when changing the database credentials. With dyanamic secrets, this could happen often. Having said that, there are workflows to work around any app limiations.

Since I was not using Vault at the time, I would generate new database credentials, redeploy the app, and failover to the new instance of the app, and tear down the old app and old credentials. This workflow happened to work okay for this application, but you may have different requirements/limitations.