Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vault: spike auto unseal with vault transit as an upgrade from the vault.sh process currently in use #64

Open
noahehall opened this issue Dec 26, 2022 · 0 comments

Comments

@noahehall
Copy link
Contributor

noahehall commented Dec 26, 2022

C

  • the unseal process is currently invoked via a script; but vault docs speak of mysterious and magical auto unseal spell

T

  • ...

A

  • auto unseal: paid
    • alicloud kms
    • aws kms [prefferred]
    • azure key vault
    • gcp cloud kms
    • oci kms
    • hsm pkcs11
  • auto unseal: free
    • vault transit
@noahehall noahehall added this to nirvai Dec 26, 2022
@noahehall noahehall converted this from a draft issue Dec 26, 2022
@noahehall noahehall changed the title vault: figure out auto unseal vault: figure out how to invoke the level 99 magical auto unseal spell Dec 26, 2022
@noahehall noahehall changed the title vault: figure out how to invoke the level 99 magical auto unseal spell vault: figure out how to invoke the level 99 magical auto unseal spell Dec 26, 2022
@noahehall noahehall changed the title vault: figure out how to invoke the level 99 magical auto unseal spell vault: figure out if auto unseal with vault transit is more robust that the vault.sh process currently in use Dec 26, 2022
@noahehall noahehall changed the title vault: figure out if auto unseal with vault transit is more robust that the vault.sh process currently in use vault: spike auto unseal with vault transit as an upgrade from the vault.sh process currently in use Dec 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: THE PITS
Development

No branches or pull requests

1 participant