Abbey Docs
  • 👋Welcome
  • Getting Started
    • Quickstart
    • Step-by-Step Tutorials
      • AWS: Managing Access to Identity Center Groups
      • AWS: Managing Access to Identity Center Permission Sets
      • AWS: Managing Access to IAM Groups
      • Azure AD: Managing Access to Groups
      • Confluent: Managing Access to Kafka ACLs
      • Databricks: Managing Access to Managed Tables in Unity Catalog
      • Databricks: Managing Access to Groups
      • GitHub: Managing Access to Teams
      • Google Cloud: Managing Access to Groups
      • Google Workspace: Managing Access to Google Groups
      • Kafka: Managing Access to ACLs
      • Okta: Managing Access to Groups
      • Postgres: Managing Access to Roles
      • Snowflake: Managing Access to Tables
      • Tabular: Managing Access to Apache Iceberg Roles
      • Tailscale: Managing Access to ACLs
      • Vault: Managing Access to Groups and Policies
      • Integrating Abbey with Terraform Cloud
      • Using Abbey with Atlantis
      • Using Abbey with Spacelift
    • Starter Kits
  • How Abbey Works
    • How Abbey Works
    • Key Concepts
  • Build a Grant Kit
    • Get a Starter Kit
    • Connect a Repo
    • Create a Grant Kit
    • Link Identities
    • Write Access Policies
    • Deploy Your Grant Kit
    • Request Access
    • Approve or Deny Access Requests
  • Use Cases
    • Time-Based Access
      • Expire After a Duration
      • Expire At a Specific Time
    • Approval Workflows
      • Using a Single Approval Step
      • Using Multiple Approval Steps
      • Conditionally Skip Approval Steps
  • Admin
    • User Roles
    • Sign-in and MFA
      • Sign-in Methods
      • Multifactor Authentication (MFA)
      • Enabling Single Sign-On
    • Sources
      • PagerDuty
      • Directory Sync
    • End User Notifications
    • Manage API Tokens
  • Reference
    • Grant Kits
      • Workflows
      • Policies
      • Outputs
    • Referencing Users and Groups
    • Linking Application Identities into Abbey
      • Why do I need to link application identities?
      • How do I Link Application Identities?
      • Supported Application Identity Types and Schemas
      • Application Data Object
    • Access Policies
      • Types of Access Policies
      • Policy Bundles
      • Inline Policies
      • Helper Functions
      • Policy Examples
    • Terms of Service
    • FAQ
      • Troubleshooting
  • Resources
    • Abbey Labs
    • Terraform Registry
    • GitHub
    • System Status
    • Privacy Policy
    • Logo
Powered by GitBook
On this page
  • Before you start
  • Step 1: Create Your User and Group
  • Step 2: Configure Your Grant Kit
  • Configure Output
  • Configure Reviewers
  • (optional) Configure AWS Region
  • Step 3: Link AWS IAM with Abbey
  • Step 4: Deploy Your Starter Kit
  • Step 5: Automate Access Management
  • Next Steps
  1. Getting Started
  2. Step-by-Step Tutorials

AWS: Managing Access to IAM Groups

PreviousAWS: Managing Access to Identity Center Permission SetsNextAzure AD: Managing Access to Groups

Last updated 3 months ago

In this tutorial, you'll learn how to configure to automate access requests to an AWS IAM Group by attaching . This use case models Role-Based Access Control (RBAC) using core AWS IAM components.

We will be using the as a base and replace configuration stubs for our use case.

Before you start

  1. Make sure you have:

    • An

    • An Abbey API Key

    • An AWS User with the policy

  2. Make sure you setup:

    • An 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

main.tf
 locals {
  account_name = "" #CHANGEME
  repo_name = "" #CHANGEME
  ...
}

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.

main.tf
 resource "abbey_grant_kit" "..." {
   ...
   workflow = {
     steps = [
       {
         reviewers = {
-          one_of = ["replace-me@example.com"] # CHANGEME
+          one_of = ["alice@example.com"]

(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.

providers.tf
provider "aws" {
  region = "us-east-1"  # CHANGEME (if necessary)
}

Step 3: Link AWS IAM with Abbey

curl -X POST \
  -H "Authorization: Bearer $ABBEY_API_TOKEN" \
  -H 'Content-Type: application/json' \
  https://api.abbey.io/v1/users/<user_id>/apps \
  -d '{"type": "aws_iam", "data": {"id": "<your AWS IAM user ID>"}}'

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.

What should it look like?

To deploy your Starter Kit, follow instructions from Deploy Your Grant Kit.

Step 5: 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.

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 Resources 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.

Now you'll need to link .

Congratulations! Abbey is now managing permissions to your Resource for you.

🎉
🎉
AWS IAM with Abbey
AWS IAM Group Memberships
AWS IAM Starter Kit
Abbey account
IAMFullAccess
AWS IAM Starter Kit
Grant Kits
Add a User
Add a Group