• Terraform Cloud
    • HCP Vault
    • HCP Consul
    • HCP Packer
  • Pricing
  • Documentation
  • Tutorials
  • Community
Sign InTry cloud for free
    • What is HCP?
      • AWS
      • Overview
        • Create and Manage HVN
        • Peering Connections
        • Transit Gateway Attachements
        • Routes
        • Security Groups
        • Overview
        • Users
        • Service Principals
        • Organizations
        • Single Sign-On
        • Multi-Factor Authentication
        • Overview
        • Payment
        • Flex Billing
      • Support
    • What is HCP Consul?
    • Specifications
      • Overview
      • Clusters
      • Clients
      • Federation
      • Upgrades
      • Audit Logs
      • Snapshots
      • Tutorials
      • Consul Documentation
      • Forums
    • Overview
    • Security Overview
    • Get Started
    • Login MFA
    • High Availability and Disaster Recovery
    • Performance Replication
    • Version Management
    • RBAC Permissions
    • Administrative Capabilities
    • Audit Log Management
      • Overview
      • FAQ
    • Metrics
    • Constraints and Known Issues
    • Migrate to HCP Vault
    • What is HCP Packer?
    • Get Started
      • Template Configuration
      • Image Metadata
      • Image Buckets
      • Image Channels and Revocation
      • Terraform Cloud Run Tasks
    • Reference Image Metadata
    • Manage Registry
    • API Reference
    • Packer Documentation
  • Glossary
  • Changelog
Type '/' to Search

»Federation

This topic describes how to federate Consul clusters in HCP.

»Introduction

Consul datacenter federation enables operators to extend their Consul environments by connecting multiple HashiCorp Cloud Platform (HCP) Consul clusters together within a region. Federation lowers the operational overhead of connecting applications across distinct regions and improves security. Server-to-server connectivity is automatically handled by the HCP platform.

»Specification

  • Clusters within the HashiCorp virtual network (HVN) must have distinct network CIDR blocks to be federated.
  • Only one cluster can be designated as the primary cluster. Clusters that you intend to designate as secondary must be added through federation.
  • Standalone clusters cannot be added to an existing federation.
  • By default, six Consul clusters are allowed in an HCP organization. As a result, one primary cluster and five secondary clusters are supported. You can request a higher limit by filing a support ticket.

Each Consul tier supports federation according to where the resources are located. Intra regional federation is when all resources are located within the same cloud provider region. Inter federation is when the resources are located across the different cloud provider regions. The following table describes the federation options for different HCP Consul tiers.

TierResource location
DevelopmentIntra regional
StandardIntra
PlusIntra (must be federated with another plus tier cluster)
Inter

»Enable Federation

  1. If you have not already done so, log into the HashiCorp Cloud Platform and click Consul under the Services sidebar menu.
  2. Either create a cluster or click on an existing cluster that you want to designate as the primary.
  3. Click Federation in the sidebar menu and click Create secondary.
  4. Configure the secondary cluster and click Create secondary. Refer to Create a Consul Cluster for information about cluster configuration options.
  5. Repeat the procedure to create additional subordinate clusters.

Tutorial: Complete the Federate Multiple HCP Consul clusters tutorial for additional guidance on enabling HCP Consul federation.

  • Learn about HCP

    • Blog
    • Press Release
  • Resources

    • Tutorials
    • Documentation
  • Help

    • Community
    • Support
    • Contact Us
  • Terms of Service
  • SLA
  • Shared Responsibility Model
  • Privacy
  • Security
  • Press Kit
©2021 HashiCorp, Inc. All rights reserved