hashicorp / hashicorp/vault-helm

AWS - Kms auto unseal not working

Open
#419 6 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Shell
Stars
1.3k
Forks
898
Avg merge
3d 1h
Merged PRs (30d)
1

Description

Hi,

We are using HashiCorp vault helm chart 0.8.0 and vault image 1.5.4 version. We've deployed this in EKS version 1.18 . We managed to unseal vault by manually however when tried the following AWS Kms for auto unseal , It didn't work .

seal "awskms" {
region = "eu-west-2"
kms_key_id = "*******"
}

First we tried deploying the helm chart with above config and it deployed with seal Type awsKms and seal set to true. We then followed the steps mentioned in this link to unseal.

https://learn.hashicorp.com/tutorials/vault/autounseal-aws-kms

After unsealing, the seal type changed to "Shamir" and seal status set to false.

but when we restarted the vault pods, it gone to CrashLoopBackOff status with below error.

**core: entering seal migration mode; Vault will not automatically unseal even if using an autoseal: from_barrier_type=shamir to_barrier_type=awskms`**

Is AWS auto unsealing process available in open source version or do we need to use enterprise version?

Contributor guide

Open the contributing guide

Research direction

Start by comparing the AWS KMS auto-unseal tutorial with the HashiCorp Vault Helm chart 0.8.0 configuration and Vault 1.5.4 error output. Investigate the Shamir-to-awskms seal migration behavior and whether the reported deployment can restart successfully with auto-unseal enabled; completion would require a confirmed configuration or documented limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, helm, kubernetes
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.