> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myrmex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon Web Services (AWS)

> Connect AWS to Myrmex — read your account configuration on demand, audit cloud posture, and remediate findings.

import { Note, Steps, Step, CardGroup, Card, Tip } from '@mintlify/components';

Connect your **Amazon Web Services (AWS)** account so Myrmex can read your resource configuration and account activity, audit your cloud security posture, and help you fix misconfigurations. Myrmex reaches the AWS APIs through a [Collector](/documentation/agent-endpoint-security/collector-mode) using a least-privilege IAM access key — everything is read in real time, on demand, and nothing from your account is stored on the Myrmex side.

## What Myrmex Can Do

<CardGroup cols={2}>
  <Card title="Read and inventory" icon="magnifying-glass">
    Enumerate services and resources — EC2, S3, IAM, VPC, and more — for real-time, read-only analysis.
  </Card>

  <Card title="Cloud posture audit" icon="shield-halved">
    Run a [Security Posture](/documentation/security-posture/overview) audit against your account using CIS, ISO 27001, and NIST controls.
  </Card>

  <Card title="Find misconfigurations" icon="triangle-exclamation">
    Surface public buckets, overly permissive IAM, unencrypted volumes, and risky security groups.
  </Card>

  <Card title="Guided remediation" icon="wrench">
    Get prioritized fixes and, on approval, apply changes to close the gaps.
  </Card>
</CardGroup>

## Before You Start

* A **Collector** deployed where it can reach the AWS APIs over HTTPS. See [Deploying the agent](/documentation/agent-endpoint-security/installation).
* An **IAM user** with programmatic access and a least-privilege policy — `ReadOnlyAccess` is enough for analysis; add narrowly scoped write permissions only when you want Myrmex to remediate.
* Your **AWS account ID** and the default **region** you work in.

## Step 1 — Create the Credential in AWS

<Steps>
  <Step title="Attach a least-privilege policy">
    In the AWS console, open **IAM → Policies** and prepare `ReadOnlyAccess`, or a tighter policy scoped to the services you want Myrmex to read.
  </Step>

  <Step title="Create an IAM user">
    Under **IAM → Users**, add a dedicated user for Myrmex and attach the policy from the previous step.
  </Step>

  <Step title="Generate an access key">
    On the user's **Security credentials** tab, create an **access key** for programmatic access. Copy the **Access Key ID** and the **Secret Access Key** — the secret is shown only once.
  </Step>
</Steps>

<Tip>
  Start with a read-only key for analysis and grant write permissions only when you want the agents to apply changes for you.
</Tip>

## Step 2 — Add the Integration in Myrmex

In the **Directory**, choose **Add Integration → Amazon Web Services (AWS)** and fill in:

| Field                 | Description                                                                                          |
| --------------------- | ---------------------------------------------------------------------------------------------------- |
| **Name**              | A unique name to identify this AWS account in Myrmex.                                                |
| **Account ID**        | Your 12-digit AWS account ID.                                                                        |
| **Region**            | The default AWS region for API calls (for example, `us-east-1`).                                     |
| **Collector**         | The [Collector](/documentation/agent-endpoint-security/collector-mode) that will reach the AWS APIs. |
| **Access Key ID**     | The IAM access key ID created in Step 1.                                                             |
| **Secret Access Key** | The secret for that access key. Stored securely and never exposed to the AI.                         |

## Connect

Click **Connect** to validate the credentials and finish. The account then appears under **Environment → Integrations**, and you can start asking the AI about it in the Workspace.

<Note>
  Prefer least privilege and rotate the access key periodically. Myrmex only needs read access for analysis; grant write permissions solely for remediation.
</Note>