HashiCorp Developer AI Private beta now available Sign up today
Consul
Consul Home

Consul Peering Generate Token

Command: consul peering generate-token

Corresponding HTTP API Endpoint: [POST] /v1/peering/token

The peering generate-token generates a peering token. The token is base 64-encoded string containing the token details. This token should be transferred to the other cluster being peered and consumed using consul peering establish.

Generating a token and specifying the same local name associated with a previously-generated token does not affect active connections established with the original token. If the previously-generated token is not actively being used for a peer connection, however, it will become invalid when the new token with the same local name is generated.

The table below shows this command's required ACLs.

ACL Required
peering:write

Usage

Usage: consul peering generate-token [options] -name <peer name>

Command Options

  • -name=<string> - (Required) Specifies a local name for the cluster that the token is intended for. The name is only used to identify the connection with the peer. Generating a token and specifying the same local name associated with a previously-generated token does not affect active connections established with the original token. If the previously-generated token is not actively being used for a peer connection, however, it will become invalid when the new token with the same local name is generated.

  • -meta=<string>=<string> - Specifies key/value pairs to associate with the peering connection token in -meta="key"="value" format. You can use the flag multiple times to set multiple metadata fields.

  • -server-external-addresses=<string>[,string,...] - Specifies a comma-separated list of addresses to put into the generated token. Addresses are of the form of {host or IP}:port. You can specify one or more load balancers or external IPs that route external traffic to this cluster's Consul servers.

  • -format={pretty|json} - Command output format. The default value is pretty.

Enterprise Options

  • -partition=<string> - Specifies the partition to query. If not provided, the partition will be inferred from the request's ACL token, or will default to the default partition. Partitions are a Consul Enterprise feature added in v1.11.0.

API Options

  • -ca-file=<value> - Path to a CA file to use for TLS when communicating with Consul. This can also be specified via the CONSUL_CACERT environment variable.

  • -ca-path=<value> - Path to a directory of CA certificates to use for TLS when communicating with Consul. This can also be specified via the CONSUL_CAPATH environment variable.

  • -client-cert=<value> - Path to a client cert file to use for TLS when verify_incoming is enabled. This can also be specified via the CONSUL_CLIENT_CERT environment variable.

  • -client-key=<value> - Path to a client key file to use for TLS when verify_incoming is enabled. This can also be specified via the CONSUL_CLIENT_KEY environment variable.

  • -http-addr=<addr> - Address of the Consul agent with the port. This can be an IP address or DNS address, but it must include the port. This can also be specified via the CONSUL_HTTP_ADDR environment variable. In Consul 0.8 and later, the default value is http://127.0.0.1:8500, and https can optionally be used instead. The scheme can also be set to HTTPS by setting the environment variable CONSUL_HTTP_SSL=true. This may be a unix domain socket using unix:///path/to/socket if the agent is configured to listen that way.

  • -tls-server-name=<value> - The server name to use as the SNI host when connecting via TLS. This can also be specified via the CONSUL_TLS_SERVER_NAME environment variable.

  • -token=<value> - ACL token to use in the request. This can also be specified via the CONSUL_HTTP_TOKEN environment variable. If unspecified, the query will default to the token of the Consul agent at the HTTP address.

  • -token-file=<value> - File containing the ACL token to use in the request instead of one specified via the -token argument or CONSUL_HTTP_TOKEN environment variable. This can also be specified via the CONSUL_HTTP_TOKEN_FILE environment variable.

Examples

The following example generates a peering token for a cluster called "cluster-02":

$ consul peering generate-token -name cluster-02
eyJDQSI6bnVs...5Yi0wNzk5NTA1YTRmYjYifQ==

Using a Load Balancer for Consul Servers

The following example generates a token for a cluster where servers are proxied by a load balancer:

$ consul peering generate-token -server-external-addresses my-load-balancer-1234567890abcdef.elb.us-east-2.amazonaws.com -name cluster-02
eyJDQSI6bnVs...5Yi0wNzk5NTA1YTRmYjYifQ==
Edit this page on GitHub