This page contains the list of deprecations and important or breaking changes for Vault 1.7.0 compared to 1.6. Please read it carefully.

»Barrier Key Auto-Rotation

If your Vault installation is at least a year old, the barrier key will be automatically rotated once, and then subsequently will be rotated per the settings in the new sys/rotate/config endpoint. This is a precaution to ensure the number of encryptions performed by the barrier key is fewer than that recommended by NIST SP 800-38D.

»AWS Auth Endpoint Changes and Deprecations

AWS Auth concepts and endpoints that use the "whitelist" and "blacklist" terms have been updated to more inclusive language (e.g. /auth/aws/identity-whitelist has been updated to/auth/aws/identity-accesslist). The old and new endpoints are aliases, sharing the same underlying data. The legacy endpoint names are considered deprecated and will be removed in a future release (not before Vault 1.9). The complete list of endpoint changes is available in the AWS Auth API docs.

»Alpine 3.14

Docker images for Vault 1.6.6+, 1.7.4+, and 1.8.2+ are built with Alpine 3.14, due to a security issue in Alpine 3.13 (CVE-2021-36159). Some users on older versions of Docker may run into issues with these images. See the following for more details:

»Known Issues

Due to the known issue, Transform Secrets Engine users are recommended to upgrade to version 1.6.4 or 1.7.0.


  • Autopilot is not currently supported on DR Secondary clusters, or in Integrated Storage's HA-only mode.
  • If the IP address in the raft peer list is different from the configured cluster address, autopilot may be unable to determine the leader node. If affected, you should disabled autopilot by setting the VAULT_RAFT_AUTOPILOT_DISABLE environment variable to 1.

»Transform Storage Upgrades Fixed

The Transform Secrets Engine storage upgrade introduced in 1.6.0 introduced malformed configuration for transformations configured earlier than 1.6.0, resulting in an error using these transformations if Vault is restarted after the upgrade. This issue exists on Vault 1.6.0 through 1.6.3, and is fixed in Vault 1.6.4 and 1.7.0. Transformations configured on 1.6.0 or higher are unaffected.