-
Notifications
You must be signed in to change notification settings - Fork 109
Keypair Rotation
This document describes what secret credentials we maintain and how to rotate them.
TODO maintain one key per environment, with playbook level vault encrypted with all keys.
The root ssh keys allow access to the ubuntu
user. These keys are only used for the initial provision of the jumpbox. After that, operators use their personal keys to access all hosts.
-
Generate a new SSH key. When prompted, set a 16+ character password. For the comment, use the key name (datagov-environment-vX).
$ ssh-keygen -f ~/.ssh/datagov-environment-vX
-
Upload the private and public keys to the shared Drive. Share the password with teammates over a secure channel.
-
For BSP environments (production and staging), create a Service Now ticket to update the SSH key in the CloudFormation templates. Attach the public key to the ticket. BSP does not need the private key.
-
For AWS Sandbox environments, import the key in the AWS Console. Update the keypair name in datagov-infrastructure-live.