2017-05-05 05:24:04 +00:00
---
2020-04-07 18:55:19 +00:00
layout: docs
page_title: Consul Enterprise
2020-04-13 18:40:26 +00:00
sidebar_title: Consul Enterprise
2020-04-07 18:55:19 +00:00
description: >-
Consul Enterprise features a number of capabilities beyond the open source
offering that may be beneficial in certain workflows.
2017-05-05 05:24:04 +00:00
---
# Consul Enterprise
2020-04-09 23:46:54 +00:00
[Consul Enterprise](https://www.hashicorp.com/consul) features ease the complexity of operating Consul at
2020-04-06 20:27:35 +00:00
organizational scale by automating common operator workflows. It introduces capabilities for expanding
performance scalability, resiliency, and cluster lifecycle. It also adds support for application and service
architectures across complex network topologies. If you have already purchased Consul Enterprise, please
2020-03-24 20:06:20 +00:00
see the [licensing section](#licensing) below.
2019-06-04 16:01:46 +00:00
Features include:
2017-05-05 05:24:04 +00:00
2020-04-09 23:20:00 +00:00
- [Automated Backups](/docs/enterprise/backups)
- [Automated Upgrades](/docs/enterprise/upgrades)
- [Enhanced Read Scalability](/docs/enterprise/read-scale)
- [Redundancy Zones](/docs/enterprise/redundancy)
- [Advanced Federation for Complex Network Topologies](/docs/enterprise/federation)
- [Network Segments](/docs/enterprise/network-segments)
- [Namespaces](/docs/enterprise/namespaces)
- [Sentinel](/docs/enterprise/sentinel)
2017-05-05 05:24:04 +00:00
These features are part of [Consul
2020-04-09 23:46:54 +00:00
Enterprise](https://www.hashicorp.com/consul).
2018-05-22 16:07:13 +00:00
## Licensing
Licensing capabilities were added to Consul Enterprise v1.1.0. The license is set
once for a datacenter and will automatically propagate to all nodes within the
datacenter over a period of time scaled between 1 and 20 minutes depending on the
2019-06-04 16:01:46 +00:00
number of nodes in the datacenter. There are two methods for licensing Consul
enterprise.
### Included in the Enterprise Package
If you are downloading Consul from Amazon S3, then the license is included
2020-04-06 20:27:35 +00:00
in the binary and you do not need to take further action. This is the
2019-06-04 16:01:46 +00:00
most common use case.
In the S3 bucket you will find three Enterprise zip packages. The packages with `+pro` and
`+prem` in the name, are the binaries that include the license. The package
with `+ent` in the name does not include the license.
### Applied after Bootstrapping
If you are downloading the enterprise binary from the [releases.hashicorp.com](https://releases.hashicorp.com/consul/) or the `+ent` package from Amazon S3, you will need to apply
2020-04-06 20:27:35 +00:00
the license to the cluster, after completing the bootstrapping process.
You can set the license on any agent within the cluster and it will be
forwarded to the leading server via the RPC forwarding functionality.
Below are your two options for setting the license file.
2019-06-04 16:01:46 +00:00
2020-04-06 20:27:35 +00:00
You can set the license via the
2020-04-09 23:46:54 +00:00
[API](/api/operator/license) or the [CLI](/docs/commands/license). When
2019-06-04 16:01:46 +00:00
you first start Consul, a 30-minute temporary license is available to allow you
time to license the datacenter. You should set the license within ten minutes of
2018-05-31 17:58:28 +00:00
starting the first Consul process to allow time for the license to propagate.
