
# HashiCorp Consul Enterprise

Commercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.

Canonical page: https://launchinyourcloud.com/directory/hashicorp-consul-enterprise/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## HashiCorp Consul Enterprise

Commercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/hashicorp-consul-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Consul Enterprise license required for the selected validated design.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform modules for AWS, Azure or Google Cloud
- Architecture: Customer-operated Consul server quorum and clients with provider load balancers, KMS, secrets and snapshot storage.
- Operations: Customer manages cluster nodes, TLS, ACLs, gossip keys, secret handling, snapshots, upgrades, service integrations and availability.
- Product website: https://www.hashicorp.com/en/products/consul
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Consul Enterprise, not HCP Consul and not the separately licensed Community Edition. The validated designs require a commercial license and production security material, including TLS certificates, ACL configuration and gossip encryption. Protect bootstrap tokens and snapshot storage and validate the selected module release before deployment. HCSEC-2026-49 and 50 cover a health-check registration authorization bypass and a consul-k8s cross-namespace ACL binding-rule bypass. Fixed builds are Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.

Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement.

Consul Enterprise runs persistent server and client agents on customer infrastructure with consensus state, snapshots and network dependencies.


### Category fit

- backend-platforms: Provides service discovery, configuration, connectivity and service-mesh control for distributed application platforms.

- devops: Automates service networking, health discovery and policy across deployment environments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (checked 2026-11-17). 


### Cloud deployment evidence

- Consul Enterprise Terraform deployments on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform
  HashiCorp provides validated Terraform deployment paths for Consul Enterprise in customer AWS, Azure and Google Cloud environments. Customers manage the deployed cluster, security material and backups.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Deploy Consul Enterprise using Terraform on AWS, Azure and Google Cloud: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform

- Consul pricing and editions: https://www.hashicorp.com/en/products/consul/pricing

- HCSEC-2026-49: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914

- HCSEC-2026-50: https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915

### Licensing sources

- https://www.hashicorp.com/en/products/consul/pricing

### Infrastructure sources

- https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The reviewed Enterprise pricing and Terraform deployment establish the licensed product, but not a current Consul Enterprise-specific Marketplace offer. HCP procurement is separate. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Consul Enterprise price/edition material did not establish qualifying Marketplace charges and commitment treatment for the buyer agreement. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. The OIDC authentication method requires self-managed Consul Enterprise 1.8.0+. It supports browser-based UI/CLI login through a configured IdP, with ACL tokens and claim mappings. Scope: Self-managed Consul Enterprise, not HCP account SSO. Source: https://developer.hashicorp.com/consul/docs/secure/acl/auth-method/oidc (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Enterprise OIDC exchanges claims for ACL tokens; it does not establish a SCIM user/group lifecycle endpoint. HCP account SCIM was excluded. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/consul/docs/secure/acl/auth-method/oidc (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HashiCorp Consul Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Security controls: Documented. The Enterprise Terraform workflow configures cluster secrets and cloud permissions. Apply ACL, TLS/gossip, backup and key-management requirements rather than treating provisioning completion as a security review. Current advisory review: HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses. Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds. Scope: Consul Enterprise deployment controls Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.. Source: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform. Supporting source: HCSEC-2026-50 — https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915.

- Air-gapped operation: Sources checked — unresolved. The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation. Scope: Self-managed Consul Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/consul/docs/enterprise/license/reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The validated design provides provider-specific Terraform deployment for Consul Enterprise on AWS, Azure and Google Cloud. Configure the licence, secrets, network access and snapshot storage before production use. Scope: Self-managed Enterprise validated Terraform deployment. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The design deploys a fault-tolerant Consul server cluster; service count, agent placement, traffic, mesh gateways and availability requirements determine total capacity. Human-user count does not size the service mesh. Scope: Consul topology and workload boundary. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- License pricing: Documented. Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement. Scope: HashiCorp Consul Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Specify service/agent count, mesh traffic, gateways and Enterprise server topology. Human users and 1 TB application data do not size a Consul service mesh. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The vendor release API identifies 2.1.0+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-22. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading. Scope: Enterprise-filtered release API snapshot; community and HCP releases excluded. Source: https://api.releases.hashicorp.com/v1/releases/consul/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/consul/2.1.0+ent/.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- HashiCorp Consul authorization-bypass updates (security-advisory): HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses. Scope: Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18. Conditions: Health-check registration permissions and Kubernetes component ACL binding rules determine exposure. Action: Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds. Source: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914; reviewed 2026-11-18. Supporting source: HCSEC-2026-50 — https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915.



