2015-05-02 21:27:35 +00:00
|
|
|
---
|
New Docs Website (#5535)
* 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
2018-10-19 15:40:11 +00:00
|
|
|
layout: "docs"
|
2015-05-02 21:27:35 +00:00
|
|
|
page_title: "Vault vs. Amazon Key Management Service"
|
New Docs Website (#5535)
* 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
2018-10-19 15:40:11 +00:00
|
|
|
sidebar_title: "Amazon KMS"
|
2015-05-02 21:27:35 +00:00
|
|
|
sidebar_current: "vs-other-kms"
|
|
|
|
description: |-
|
|
|
|
Comparison between Vault and Amazon Key Management Service.
|
|
|
|
---
|
|
|
|
|
|
|
|
# Vault vs. Amazon KMS
|
|
|
|
|
2016-08-22 13:19:13 +00:00
|
|
|
Amazon Key Management Service (KMS) is a service provided in the AWS ecosystem
|
|
|
|
for encryption key management. It is backed by Hardware Security Modules (HSM)
|
|
|
|
for physical security.
|
2015-05-02 21:27:35 +00:00
|
|
|
|
2016-08-22 13:19:13 +00:00
|
|
|
Vault and KMS differ in the scope of problems they are trying to solve. KMS is
|
|
|
|
focused on securely storing encryption keys and supporting cryptographic
|
|
|
|
operations (encrypt and decrypt) using those keys. It supports access controls
|
|
|
|
and auditing as well.
|
2015-05-02 21:27:35 +00:00
|
|
|
|
2016-08-22 13:19:13 +00:00
|
|
|
In contrast, Vault provides a comprehensive secret management solution. The
|
|
|
|
[`transit` backend](/docs/secrets/transit/index.html) provides similar
|
|
|
|
capabilities as KMS, allowing for encryption keys to be stored and
|
|
|
|
cryptographic operations to be performed. However, Vault goes much further than
|
|
|
|
just key management.
|
2015-05-02 21:27:35 +00:00
|
|
|
|
2017-09-20 20:05:00 +00:00
|
|
|
The flexible secrets engines allow Vault to handle any type of secret data,
|
2016-08-22 13:19:13 +00:00
|
|
|
including database credentials, API keys, PKI keys, and encryption keys. Vault
|
|
|
|
also supports dynamic secrets, generating credentials on-demand for
|
2015-05-02 21:27:35 +00:00
|
|
|
fine-grained security controls, auditing, and non-repudiation.
|
|
|
|
|
2018-01-15 19:33:41 +00:00
|
|
|
Lastly, Vault forces a mandatory lease contract with clients. All secrets read
|
2016-08-22 13:19:13 +00:00
|
|
|
from Vault have an associated lease which enables operations to audit key
|
|
|
|
usage, perform key rolling, and ensure automatic revocation. Vault provides
|
2016-09-01 13:53:20 +00:00
|
|
|
multiple revocation mechanisms to give operators a clear "break glass"
|
2016-08-22 13:19:13 +00:00
|
|
|
procedure after a potential compromise.
|
2015-05-02 21:27:35 +00:00
|
|
|
|
2016-08-22 13:19:13 +00:00
|
|
|
Vault is an open source tool that can be deployed to any environment, and does
|
|
|
|
not require any special hardware. This makes it well suited for cloud
|
2015-05-02 21:27:35 +00:00
|
|
|
environments where HSMs are not available or are cost prohibitive.
|