---
layout: docs
page_title: Service Mesh - What is Cluster Peering?
description: >-
  Cluster peering establishes communication between independent clusters in Consul, allowing services to interact across datacenters. Learn about the cluster peering process, differences with WAN federation for multi-datacenter deployments, and technical constraints.  
---

# What is Cluster Peering?

You can create peering connections between two or more independent clusters so that services deployed to different partitions or datacenters can communicate.

## Overview

Cluster peering is a process that allows Consul clusters to communicate with each other. The cluster peering process consists of the following steps:

1. Create a peering token in one cluster.
1. Use the peering token to establish peering with a second cluster.
1. Export services between clusters.
1. Create intentions to authorize services for peers.

This process establishes cluster peering between two [admin partitions](/docs/enterprise/admin-partitions). Deployments without an Enterprise license can still use cluster peering because every datacenter automatically includes a `default` partition.

For detailed instructions on establishing cluster peering connections, refer to [Create and Manage Peering Connections](/docs/connect/cluster-peering/create-manage-peering).

> To learn how to peer clusters and connect services across peers in AWS Elastic Kubernetes Service (EKS) environments, complete the [Consul Cluster Peering on Kubernetes tutorial](https://learn.hashicorp.com/tutorials/consul/cluster-peering-aws?utm_source=docs).

### Differences between WAN federation and cluster peering

WAN federation and cluster peering are different ways to connect Consul deployments. WAN federation connects multiple datacenters to make them function as if they were a single cluster, while cluster peering treats each datacenter as a separate cluster. As a result, WAN federation requires a primary datacenter to maintain and replicate global states such as ACLs and configuration entries, but cluster peering does not.

Regardless of whether you connect your clusters through WAN federation or cluster peering, human and machine users can use either method to discover services in other clusters or dial them through the service mesh.

|                                                    | WAN Federation | Cluster Peering |
| :------------------------------------------------- | :------------: | :-------------: |
| Connects clusters across datacenters               |    &#9989;     |    &#9989;      |
| Shares support queries and service endpoints       |    &#9989;     |    &#9989;      |
| Connects clusters owned by different operators     |    &#10060;    |    &#9989;      |
| Functions without declaring primary datacenter     |    &#10060;    |    &#9989;      |
| Replicates exported services for service discovery |    &#10060;    |    &#9989;      |
| Gossip protocol: Requires LAN gossip only          |    &#10060;    |    &#9989;      |
| Forwards service requests for service discovery    |    &#9989;     |    &#10060;     |
| Shares key/value stores                            |    &#9989;     |    &#10060;     |
| Can replicate ACL tokens, policies, and roles      |    &#9989;     |    &#10060;     |

## Important Cluster Peering Constraints

Consider the following technical constraints:

- Services with node, instance, and check definitions totaling more than 8MB cannot be exported to a peer.
- Two admin partitions in the same datacenter cannot be peered. Use [`exported-services`](/docs/connect/config-entries/exported-services#exporting-services-to-peered-clusters) directly.
- The `consul intention` CLI command is not supported. To manage intentions that specify services in peered clusters, use [configuration entries](/docs/connect/config-entries/service-intentions).
- Accessing key/value stores across peers is not supported.
