AWS: Managing Access to IAM Groups
In this tutorial, you'll learn how to configure Grant Kits to automate access requests to an AWS IAM Group by attaching AWS IAM Group Memberships. This use case models Role-Based Access Control (RBAC) using core AWS IAM components.
We will be using the AWS IAM Starter Kit as a base and replace configuration stubs for our use case.
Before you start
Make sure you have:
An Abbey API Key
An AWS User with the IAMFullAccess policy
Make sure you setup:
An AWS IAM Starter Kit by following Get a Starter Kit
A Connection to a repo by following Connect a Repo
Step 1: Create Your User and Group
In the AWS IAM Console, create a new user and group. Do not add the user to the group at this time.
Step 2: 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.
(optional) Configure AWS Region
The default for this Starter Kit uses us-east-1
. If your AWS infrastructure is in another region, you can replace it in providers.tf
.
Step 3: Link AWS IAM with Abbey
Now you'll need to link AWS IAM with Abbey.
Step 4: Deploy Your Starter Kit
First, add your GitHub-related secrets to your repo's repository secrets:
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
ABBEY_TOKEN
You can find the AWS keys in your AWS account.
The ABBEY_TOKEN is your API key.
To deploy your Starter Kit, follow instructions from Deploy Your Grant Kit.
Step 5: Automate Access Management
🎉 Congratulations! Abbey is now managing permissions to your Resource for you. 🎉
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.
After approving the request, you should be able to see that the User has been added to the Group in the AWS console.
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