Skip to content

fix(openbao): enable AWS KMS auto-unseal on scaleway #12

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.

Sign up for GitHub

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

Merged
nbrieussel merged 1 commit into from
Jul 21, 2026
+18 −0
Merged

fix(openbao): enable AWS KMS auto-unseal on scaleway #12

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions platform/scaleway/openbao.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,17 @@ spec:
server:
ha:
enabled: false
# AWS credentials the awskms seal authenticates with. OpenBao must read
# these at startup to unseal — they cannot come from OpenBao itself
# (chicken-and-egg). Secret created out-of-band by 02-cluster/scaleway
# terraform; values originate from 03-backup/scaleway kms.tf.
extraSecretEnvironmentVars:
- envName: AWS_ACCESS_KEY_ID
secretName: openbao-unseal-aws
secretKey: AWS_ACCESS_KEY_ID
- envName: AWS_SECRET_ACCESS_KEY
secretName: openbao-unseal-aws
secretKey: AWS_SECRET_ACCESS_KEY
standalone:
config: |
ui = true
Expand All @@ -28,6 +39,13 @@ spec:
path = "/openbao/data"
node_id = "openbao-0"
}
# Auto-unseal via AWS KMS. region + kms_key_id are non-secret
# (the IAM creds above gate access). On first `bao operator init`
# this yields RECOVERY keys, not unseal keys — store them safely.
seal "awskms" {
region = "eu-west-3"
kms_key_id = "367e11de-75f4-4df0-a038-b6cf06ae2ead"
}

destination:
server: https://kubernetes.default.svc
Expand Down
Loading