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

Vault Database Secret Engine Integration With Boundary Credential Library. #50

Open
Shayan-Ghani opened this issue Sep 1, 2024 · 0 comments
Labels
ansible ansible-related issues Boundary Boundary-related issues enhancement New feature or request terraform this regards Terraform related stuff Vault Vault-related issues

Comments

@Shayan-Ghani
Copy link
Member

According to a quick start tutorial on Hashicorp's gituhb page a demo postgres database target is deployed. Vault server is then configured using the database secrets engine and policies allowing Boundary to request credentials for two roles, a DBA and an "analyst". Boundary DBA and analyst targets are configured using a credential store that contains credential libraries for both targets. This enables credential brokering via Vault, which is demonstrated using the boundary connect postgres command.

Instead of running the commands imperatively use Ansible, Docker-Compose, and Terraform to do the Job for You.

@Shayan-Ghani Shayan-Ghani added enhancement New feature or request terraform this regards Terraform related stuff ansible ansible-related issues Vault Vault-related issues Boundary Boundary-related issues labels Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ansible ansible-related issues Boundary Boundary-related issues enhancement New feature or request terraform this regards Terraform related stuff Vault Vault-related issues
Projects
None yet
Development

No branches or pull requests

1 participant