Consul Enterprise Namespaces

This feature requires HashiCorp Cloud Platform (HCP) or self-managed Consul Enterprise. Refer to the enterprise feature matrix for additional information.

With Consul Enterprise 1.7.0+, data for different users or teams can be isolated from each other with the use of namespaces. Namespaces help reduce operational challenges by removing restrictions around uniqueness of resource names across distinct teams, and enable operators to provide self-service through delegation of administrative privileges.

For more information on how to use namespaces with Consul Enterprise please review the following HashiCorp Learn Guides:

• - Register multiple services within different namespaces in Consul.

An example namespace definition looks like the following:

JSON

• JSON
• HCL

• ACLs (object: <optional>) - This fields is a nested JSON/HCL object to contain the namespaces ACL configuration.

  • (array<ACLLink>) - A list of default policies to be applied to all tokens created in this namespace. The ACLLink object can contain an and/or Name field. When the policies ID is omitted Consul will resolve the name to an ID before writing the namespace definition internally. Note that all policies linked in a namespace definition must be defined within the default namespace, and the ACL token used to create or edit the namespace must have acl:write access to the linked policy.