source control • Unified management to secrets for the multitude of systems ◦ AWS ◦ Database server ◦ ... • Short lived credentials • Full audit trail of any secret access • Revocation ◦ Per credential ◦ Per user ◦ Per system
Backend Give Vault just enough rights to create access secrets: • Create an IAM user manually • Assign it a role only allowing it to create IAM users or STS tokens • Configure Vault with a keypair of that user Vault CLI • Give Vault a GitHub API token • Set the GitHub org that has access • Map Github org teams to profiles
profiles? Vault has a similar Auth backend: AWS-EC2 • Instance identity document: PKCS#7 doc signed by AWS • Public keys published by AWS per region • Vault checks the signature & the current EC2 instance running status • Using tags as roles for authorization purposes