# AWS: Managing Access to Identity Center Groups

In this tutorial, you'll learn how to configure [Key Concepts](/how-abbey-works/concepts.md#grant-kits) to automate access requests to an AWS Identity Center Group by attaching AWS Identity Center Group Membership resources. This use case models Role-Based Access Control (RBAC) using AWS Identity Center Groups.

This example has two accounts and two groups; we model access to a Staging and a Production account. Here we have two groups: R\&D and Prod Access. Members of the R\&D groups are allowed full access to resources within the Staging account and read-only access to resources within the Production Account. Members of the Prod Access group are given full access to EC2 and S3 inside the Production Account.

We will be using Abbey to allow a user to request EC2 or S3 access to the Production account by being adding them to the Prod Access group.

## Before you start

1. **Make sure you have:**
   * An [Abbey account](https://app.abbey.so/sign-up)
   * An [Abbey API Token](/admin/managing-api-tokens.md#creating-new-api-tokens)
   * An AWS Identity Center instance with the [IAMFullAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/IAMFullAccess.html) policy
2. **Make sure you setup:**
   * An [AWS Identity Center Starter Kit](https://github.com/abbeylabs/abbey-starter-kit-aws-identity-center-groups) by following [Get a Starter Kit](/build-a-grant-kit/get-a-starter-kit.md)
   * A Connection to a repo by following [Connect a Repo](/build-a-grant-kit/connect-a-repo.md)

## Step 1: Create Accounts Resources

The starter kit has two example accounts, *Staging* and *Production*, to get you started.

{% code title="accounts.tf" %}

```diff
resource "aws_organizations_account" "staging" {
  name = "Staging"
-  email = "replace-me@example.com" #CHANGEME
+  email = "staging_owner@example.com" # Use the email of an account in Identity Center.
}

resource "aws_organizations_account" "production" {
  name = "Production"
-  email = "replace-me@example.com" #CHANGEME
+  email = "production_owner@example.com" # Use the email of an account in Identity Center.
}
```

{% endcode %}

## 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`

{% code title="main.tf" %}

```hcl
 locals {
  account_name = "" #CHANGEME
  repo_name = "" #CHANGEME
  ...
}
```

{% endcode %}

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

{% code title="main.tf" %}

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

{% endcode %}

## Step 3: Link AWS Identity Center with Abbey

Now you'll need to link [AWS Identity Center with Abbey](https://developers.abbey.io/#operation/createAppData). 

{% code title="" %}

```diff

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_identitystore", "data": {"id": "<your AWS Identity Center user ID>"}}'
```

{% endcode %}

## 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 token.

<details>

<summary>What should it look like?</summary>

<img src="/files/lkVnjzRO5AHI0ATdbHyd" alt="" data-size="original">

</details>

To deploy your Starter Kit, follow instructions from [Deploy Your Grant Kit](/build-a-grant-kit/deploying-your-grant-kit.md).

## Step 5: Automate Access Management

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

You can now start requesting and approving access by following the [Request Access](/build-a-grant-kit/requesting-access.md) and [Approve or Deny Access Requests](/build-a-grant-kit/approving-or-denying-access-requests.md) guides.

{% hint style="success" %}
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.
{% endhint %}

After approving the request, you should be able to see that the Identity Center User has been added to the Group in the AWS Identity Center console, and that they have an associated AWS Identity Center Permission Set for the account where the assignment was made.

<figure><img src="/files/k58fVmeOD5vdC9TBOywk" alt=""><figcaption><p>Read-Only Access to the Production account for this user</p></figcaption></figure>

## Next Steps

To learn more about what [Resources](/resources/privacy-policy.md) you can configure, try one of our [Step-by-Step Tutorials](/getting-started/tutorials.md).

For more information on how Abbey works, visit the [Key Concepts](/how-abbey-works/concepts.md) or [Grant Kits](/reference/grant-kits.md) page.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.abbey.io/getting-started/tutorials/aws-managing-access-to-identity-center-groups-and-accounts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.