awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-06 14:27:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update hsm-integration.mdx

Browse Source
This commit is contained in:
Daniel Hougaard
2025-10-10 16:50:55 +04:00
parent 24595c405c
commit 9e60350b89
1 changed files with 15 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/documentation/platform/kms/hsm-integration.mdx
+15 -14
View File
@@ -370,7 +370,7 @@ Enabling HSM encryption has a set of key benefits:
</Accordion> </Accordion>
</AccordionGroup> </AccordionGroup>
At this point it is assumed that you have: At this point you should have:
1. [Activated the CloudHSM cluster](https://docs.aws.amazon.com/cloudhsm/latest/userguide/activate-cluster.html) 1. [Activated the CloudHSM cluster](https://docs.aws.amazon.com/cloudhsm/latest/userguide/activate-cluster.html)
2. [Created a Crypto User HSM user](https://docs.aws.amazon.com/cloudhsm/latest/userguide/cloudhsm_cli-user-create.html) 2. [Created a Crypto User HSM user](https://docs.aws.amazon.com/cloudhsm/latest/userguide/cloudhsm_cli-user-create.html)
3. Downloaded and configured the CloudHSM client as described in the previous steps. 3. Downloaded and configured the CloudHSM client as described in the previous steps.
@@ -1034,7 +1034,7 @@ Enabling HSM encryption has a set of key benefits:
</Accordion> </Accordion>
</AccordionGroup> </AccordionGroup>
At this point it is assumed that you have: At this point you should have:
1. [Activated the CloudHSM cluster](https://docs.aws.amazon.com/cloudhsm/latest/userguide/activate-cluster.html) 1. [Activated the CloudHSM cluster](https://docs.aws.amazon.com/cloudhsm/latest/userguide/activate-cluster.html)
2. [Created a Crypto User HSM user](https://docs.aws.amazon.com/cloudhsm/latest/userguide/cloudhsm_cli-user-create.html) 2. [Created a Crypto User HSM user](https://docs.aws.amazon.com/cloudhsm/latest/userguide/cloudhsm_cli-user-create.html)
3. Downloaded and configured the CloudHSM client as described in the previous steps. 3. Downloaded and configured the CloudHSM client as described in the previous steps.
@@ -1251,20 +1251,20 @@ Enabling HSM encryption has a set of key benefits:
```yaml ```yaml
# ... The rest of the values.yaml file ... # ... The rest of the values.yaml file ...
infisical:
image: image:
repository: infisical/infisical repository: infisical/infisical
tag: "v0.117.1-postgres" tag: "v0.117.1-postgres"
pullPolicy: IfNotPresent pullPolicy: IfNotPresent
extraVolumeMounts: extraVolumeMounts:
- name: cloudhsm-data - name: cloudhsm-data
mountPath: /opt/cloudhsm # The path we will mount the HSM client files to mountPath: /opt/cloudhsm # The path we will mount the HSM client files to
extraVolumes: extraVolumes:
- name: cloudhsm-data - name: cloudhsm-data
persistentVolumeClaim: persistentVolumeClaim:
claimName: cloudhsm-data-pvc # The PVC we created in the previous step claimName: cloudhsm-data-pvc # The PVC we created in the previous step
# ... The rest of the values.yaml file ... # ... The rest of the values.yaml file ...
``` ```
@@ -1279,6 +1279,7 @@ Enabling HSM encryption has a set of key benefits:
After updating the values.yaml file, you need to upgrade the Helm chart in order for the changes to take effect. After updating the values.yaml file, you need to upgrade the Helm chart in order for the changes to take effect.
```bash ```bash
helm repo update
helm upgrade --install infisical infisical-helm-charts/infisical-standalone --values /path/to/values.yaml helm upgrade --install infisical infisical-helm-charts/infisical-standalone --values /path/to/values.yaml
``` ```
</Step> </Step>