# Consensus Node Secrets Database Encryption Requirement for mainnet17

**URL:** <https://forum.flow.com/t/consensus-node-secrets-database-encryption-requirement-for-mainnet17/2876>\
**Category:** Node Operations\
**Tags:** consensus\
**Created:** [March 1, 2022, 7:52pm UTC](https://forum.flow.com/t/consensus-node-secrets-database-encryption-requirement-for-mainnet17/2876 "2022-03-01T19:52:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vishal](https://avatars.discourse-cdn.com/v4/letter/v/49beb7/32.png) [@vishal](https://forum.flow.com/u/vishal)\
**Post date:** [March 1, 2022, 7:52pm UTC](https://forum.flow.com/t/consensus-node-secrets-database-encryption-requirement-for-mainnet17/2876/1 "2022-03-01T19:52:58Z")

</div>

Hello **Consensus node** operators,

In Mainnet17, consensus nodes will be required to encrypt their secrets database. Operators will be required to generate a secrets database encryption key if they have not already done so. If the key does not exist the node will fail to start, unless the node operator explicitly disables encryption using the (`--insecure-secrets-db`) flag.

**This change will go into effect:**

**MainNet:** April, 2022

**Who/What This Impacts**

Consensus node operators that have not yet setup a secrets database encryption key.

**Action Required**

1. Enable encryption for the secrets database.

Please follow [this guide](https://docs.onflow.org/node-operation/db-encryption-existing-operator/) to generate an encryption key and enable encryption for the secrets database.

If you have any questions regarding this, please reach out for assistance on [the Flow Discord](https://github.com/onflow/comms/blob/b087cf1bf6ce03c09ae0235ee73f96800823f4bc/documents/onflow.org/discord).

1. If the encryption key is not generated in time prepare to add a new flag denoting insecure secrets database usage (`--insecure-secrets-db`)

Thank you