a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
33 lines
1.4 KiB
Markdown
33 lines
1.4 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Vault vs. Consul"
|
|
sidebar_title: "Consul"
|
|
sidebar_current: "vs-other-consul"
|
|
description: |-
|
|
Comparison between Vault and attempting to store secrets with Consul.
|
|
---
|
|
|
|
# Vault vs. Consul
|
|
|
|
[Consul](https://www.consul.io) is a system for service discovery, monitoring,
|
|
and configuration that is distributed and highly available. Consul also
|
|
supports an ACL system to restrict access to keys and service information.
|
|
|
|
While Consul can be used to store secret information and gate access using
|
|
ACLs, it is not designed for that purpose. As such, data is not encrypted
|
|
in transit nor at rest, it does not have pluggable authentication mechanisms,
|
|
and there is no per-request auditing mechanism.
|
|
|
|
Vault is designed from the ground up as a secret management solution. As such,
|
|
it protects secrets in transit and at rest. It provides multiple authentication
|
|
and audit logging mechanisms. Dynamic secret generation allows Vault to avoid
|
|
providing clients with root privileges to underlying systems and makes
|
|
it possible to do key rolling and revocation.
|
|
|
|
The strength of Consul is that it is fault tolerant and highly scalable.
|
|
By using Consul as a backend to Vault, you get the best of both. Consul
|
|
is used for durable storage of encrypted data at rest and provides coordination
|
|
so that Vault can be highly available and fault tolerant. Vault provides
|
|
the higher level policy management, secret leasing, audit logging, and automatic
|
|
revocation.
|