---
title: "Connect Amazon Web Services | Proofline Help"
description: "Connect an AWS account so Proofline can read infrastructure evidence through a role you create in that account."
url: https://proofline.sh/help/connect-aws/
---

[Help center](/help/)

# Connect Amazon Web Services

Connect an AWS account so Proofline can read infrastructure evidence through a role you create in that account.

[![Production AWS account with Connected status.](/help-images/aws-light.png)](/help-images/aws-light.png)

The account appears here after you connect it. Fictional demo workspace.

## Start the connection

1.  Open **Settings → Connections** and find AWS connections.
2.  Select **Connect an AWS account**.
3.  Enter the **Target AWS account ID** and **Installation region** on the **Setup** tab.
4.  Select **Continue** to choose an installation method.

Use **Status** to check connection status and **Setup** to install the role. Open **Diagnostics** for the last check and issued role values, and **Access request** for inventory reads AWS refused. To name the connection, open **Settings** and edit **Name**; **Save** appears when the name changes.

Review the supplied role template before applying it. Use the trust information provided for this connection, including its external ID.

## Create the role

**AWS console (recommended)** opens browser-based CloudFormation setup. Choose **Infrastructure code** for Terraform, SST v3, or Pulumi TypeScript, **AWS CLI** for a terminal, or **Your coding agent** to let Claude Code, Codex or another agent on your machine create the stack. If browser installation is unavailable, Proofline shows the CLI fallback.

Enter the **Target AWS account ID** and **Installation region**. Select the account that owns the infrastructure you want Proofline to read. The region selects the CloudFormation stack or infrastructure provider. IAM roles are account-wide; you configure evidence regions separately when linking the account to an environment.

-   [Choose which AWS reads to grant](/help/aws-select-reader-permissions/)
-   [Install or update the AWS reader with CloudFormation](/help/aws-browser-installation/)
-   [Install the AWS reader role from a terminal](/help/aws-cli-reader-installation/)

### Installation permissions

[Resolve missing AWS installer permissions](/help/aws-installer-permissions/).

### Apply with your chosen tool

-   [Finish a multi-account AWS StackSet installation](/help/aws-stackset-instances/)
-   [Install and verify the AWS role with your coding agent](/help/aws-agent-reader-installation/)
-   [Manage the AWS reader role in infrastructure code](/help/aws-reader-infrastructure-code/)
-   [Apply a permissions boundary to the AWS reader](/help/aws-reader-boundary/)
-   [Verify a newly installed AWS reader role](/help/aws-check-role-access/)

## Verify the role

-   [Diagnose a failed AWS reader installation](/help/aws-reader-troubleshooting/)
-   [Resume or discard an unfinished AWS connection](/help/aws-pending-connection/)

## Connect the evidence to an environment

Open the environment's **Setup → AWS accounts** page and use **Add**. Select a connected account, set its region, and select **Link account**. Proofline collects the account's inventory in that region. If the environment runs on ECS, add each cluster with the services it deploys to, so deploy verification can follow them. If it runs on EKS, name its cluster and namespaces in [the AWS account page's EKS cluster section](/help/environment-aws-account/), which appears once the account is linked.

To connect a new account from this page, select **Connect an AWS account**. Proofline opens the account's page, where **Open AWS connection** opens its connection. Pending accounts in the list open that page too. Once the account connects, set its region and link it.

[Repair refused AWS inventory reads](/help/aws-inventory-access-request/).

An account connection grants the configured infrastructure access. It does not establish that every service or database is covered.

## Checking the reader and its inventory

-   [Find which AWS resource types an environment could not read](/help/aws-inventory-diagnostics-by-environment/)
-   [Apply an AWS access request through the role’s owning installer](/help/aws-access-request-policy-owner/)

## Related guides

-   [Prepare Terraform changes](/help/terraform-changes/)
-   [Create an environment](/help/create-environment/)
-   [Turn on the production loop for AWS](/help/aws-production-loop/)
