Clarify encrypt key for WAN joined DCs

This commit is contained in:
Brian Shumate 2018-03-02 10:41:09 -05:00
parent 4605d4ed0b
commit 6d92c28c5c
1 changed files with 2 additions and 0 deletions

View File

@ -18,6 +18,8 @@ Enabling gossip encryption only requires that you set an encryption key when
starting the Consul agent. The key can be set via the `encrypt` parameter: the starting the Consul agent. The key can be set via the `encrypt` parameter: the
value of this setting is a configuration file containing the encryption key. value of this setting is a configuration file containing the encryption key.
~> **WAN Joined Datacenters Note:** If using multiple WAN joined datacenters, be sure to use _the same encryption key_ in all datacenters.
The key must be 16-bytes, Base64 encoded. As a convenience, Consul provides the The key must be 16-bytes, Base64 encoded. As a convenience, Consul provides the
[`consul keygen`](/docs/commands/keygen.html) command to generate a [`consul keygen`](/docs/commands/keygen.html) command to generate a
cryptographically suitable key: cryptographically suitable key: