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

Update Vault Certificate #22

Open
3 tasks
s-newman opened this issue Oct 13, 2019 · 1 comment
Open
3 tasks

Update Vault Certificate #22

s-newman opened this issue Oct 13, 2019 · 1 comment
Labels
automation Updating or improving existing automation utilities configuration Making modifications to existing services management This issue relates to services that are used internally by the Operations Program

Comments

@s-newman
Copy link
Collaborator

Update Vault Certificate

The HashiCorp Vault certificate is currently from LetsEncrypt's staging environment. This is not accepted by any browsers or operating systems, so we should switch to a certificate from the production environment. This will also help us test our procedure for updating LetsEncrypt certificates that have been issued through Terraform.

Tasks

All of the following tasks must be complete before this issue can be closed. Be sure to reference this issue in the relevant issues/PRs in other repositories.

  • Update Vault with a valid certificate
  • Update Terraform, Ansible, or other relevant automation
  • Document how to update a host's LetsEncrypt cert with our Terraform
@s-newman s-newman added management This issue relates to services that are used internally by the Operations Program configuration Making modifications to existing services automation Updating or improving existing automation utilities labels Oct 13, 2019
@s-newman
Copy link
Collaborator Author

Since certificates are deployed to the host at creation time via cloud-init, I suspect that we will have to do this by redeploying the vault instance and migrating the EBS volume to the new instance. Ideally, only the instance should be destroyed and all other Terraform resources should be left intact (reconfiguration acceptable).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation Updating or improving existing automation utilities configuration Making modifications to existing services management This issue relates to services that are used internally by the Operations Program
Projects
None yet
Development

No branches or pull requests

1 participant