Postgres: Managing Access to Roles
We will be using the Postgres Starter Kit as a base and replace configuration stubs for our use case.
Before you start
Make sure you have:
Make sure you setup:
A Postgres Starter Kit by following Get a Starter Kit
A Connection to a repo by following Connect a Repo
Step 1: Configure Your Grant Kit
Configure Output
Grant Kits rely on your GitHub account and repository name to output access changes, which we'll set through Terraform local variables. Update the locals
block in main.tf
with your account_name
and repo_name
Configure Reviewers
Workflow defines who should approve an access request.
Let's update the reviewers
block by adding yourself as the reviewer by switching replace-me@example.com
with the email address you use to sign into Abbey.
Step 2: Link Postgres with Abbey
Now you'll need to link Postgres with Abbey.
Step 3: Deploy Your Starter Kit
First, add your GitHub-related secrets to your repo:
PG_PASSWORD
You can optionally set the following variables as secrets or just provide a default.
To deploy your Starter Kit, follow instructions from Deploy Your Grant Kit.
Step 4: Automate Access Management
You can now start requesting and approving access by following the Request Access and Approve or Deny Access Requests guides.
Abbey strives to help you automate and secure access management without being intrusive.
To that end, this Pull Request contains native Terraform HCL code using normal open source Terraform Provider libraries. It represents the permissions change. In this case, it's just a simple creation of a new Terraform Resource.
Next Steps
To learn more about what Privacy Policy you can configure, try one of our Step-by-Step Tutorials.
For more information on how Abbey works, visit the Key Concepts or Grant Kits page.
Last updated