secret are removing when vault server is closed

Hi Vineesha

The behavior you described is expected when using a Vault server in its default configuration. When you create a secret in Vault and the server is running, the secret is stored temporarily in the Vault's in-memory storage engine.

When you shut down the Vault server, all data stored in the in-memory storage engine is lost. This is the default behavior to ensure the security of sensitive data. Vault is designed to persist secrets securely and prevent unauthorized access even if the underlying storage is compromised.

To solve this issue and persist secrets beyond the lifetime of the Vault server, you need to configure Vault to use a durable storage backend. This allows Vault to store secrets in a persistent data store, such as a file system, a database, or a cloud storage solution.

Here are the general steps to configure a durable storage backend for Vault:

1. Choose a durable storage backend: Determine which storage backend you want to use, such as Consul, PostgreSQL, MySQL, or AWS S3. The choice depends on your requirements and infrastructure.

2. Install and configure the storage backend: Set up and configure the chosen storage backend according to the specific instructions provided by the Vault documentation. Each storage backend has its own configuration requirements.

3. Configure Vault to use the storage backend: Update the Vault configuration file to specify the details of the storage backend. This typically involves providing connection information, authentication credentials, and any other required settings.

4. Restart the Vault server: After configuring the storage backend, restart the Vault server. It will now use the durable storage backend to persist secrets.

If you find this answer useful kindly accpt