Vault
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/edge | 89 | 31 Jan 2024 | |
| latest/edge | 9 | 27 Jan 2023 | |
| 1.16/stable | 502 | 20 Feb 2026 | |
| 1.16/candidate | 502 | 19 Feb 2026 | |
| 1.16/beta | 502 | 19 Feb 2026 | |
| 1.16/edge | 502 | 19 Feb 2026 | |
| 2.0/candidate | 565 | 01 Jul 2026 | |
| 2.0/beta | 565 | 23 Jun 2026 | |
| 2.0/edge | 571 | 03 Jul 2026 | |
| 2.0/edge | 570 | 02 Jul 2026 | |
| 2.0/edge | 569 | 02 Jul 2026 | |
| 1.19/stable | 528 | 21 Apr 2026 | |
| 1.19/candidate | 528 | 03 Apr 2026 | |
| 1.19/beta | 528 | 03 Apr 2026 | |
| 1.19/edge | 544 | 04 May 2026 | |
| 1.19/edge | 543 | 04 May 2026 | |
| 1.18/stable | 534 | 01 Jul 2026 | |
| 1.18/candidate | 534 | 01 Jul 2026 | |
| 1.18/beta | 534 | 01 Jul 2026 | |
| 1.18/edge | 534 | 09 Apr 2026 | |
| 1.17/stable | 354 | 11 Apr 2025 | |
| 1.17/candidate | 354 | 11 Apr 2025 | |
| 1.17/beta | 383 | 14 Jul 2025 | |
| 1.17/edge | 491 | 12 Jan 2026 | |
| 1.15/stable | 248 | 24 Jul 2024 | |
| 1.15/candidate | 248 | 24 Jul 2024 | |
| 1.15/beta | 248 | 24 Jul 2024 | |
| 1.15/edge | 248 | 10 Jul 2024 |
juju deploy vault-k8s --channel 1.19/stableUse Vault as an ACME Server to obtain TLS certificates
In this how-to guide, we will configure Vault to act as an ACME server using Vault’s PKI secrets engine. Here self-signed-certificates will be the parent CA.
The certificates issued by Vault will have a validity period that is half of its intermediate CA’s, which is determined by the root provider’s configuration, in this case, the self-signed certificates.
- Configure Vault’s common name
juju config vault common_name=mydomain.com
- Deploy the parent CA
juju deploy self-signed-certificates --channel 1/stable
- Integrate Vault with its parent CA
juju integrate vault:tls-certificates-acme self-signed-certificates
Now the ACME server is accessible on https://<Vault Address>:8200/v1/charm-acme/acme/directory
Now you should be able to obtain a certificate from Vault using an ACME client, for example Lego.