> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/connectors/aws.md).

# AWS

## Overview

Connect AWS to Nullify for cloud-to-code traceability. The connector deploys a least-privilege cross-account role so the platform can ingest resource metadata, evaluate exposure, and correlate findings with the code that built those resources.

## Key Benefits

* **Cloud-to-code mapping** — Tie vulnerabilities back to specific AWS accounts, regions, and IaC definitions.
* **Blast-radius awareness** — Understand which services, identities, and networks are reachable from an exposed asset.
* **Multi-account coverage** — Operate across entire AWS Organizations with consistent policy.
* **Secure access** — Uses external IDs, scoped IAM roles, and encrypted transport.

## How It Works

1. Configure connector parameters in the Nullify console.
2. Deploy the generated CloudFormation or Terraform template into each AWS account.
3. Nullify validates the role and begins ingesting metadata for cloud exposure assessments.

Full setup instructions, parameters, and troubleshooting are documented in [Configuration](/connectors/aws/configuration.md).

## Support

* Implementation assistance: <support@nullify.ai>
* Feature requests: [GitHub issue tracker](https://github.com/nullify-platform/feature-requests)

Telemetry and findings flow back asynchronously into Jira, Slack, and Nullify dashboards so remediation stays aligned with cloud owners.

## Deployment choices

The [cloud connector repository](https://github.com/Nullify-Platform/nullify-cloud-connector/tree/main/aws-integration-setup) provides CloudFormation, Terraform for AWS provider v5, and a separate `terraform-v6` variant. Use the variant matching your provider version. Multi-cluster EKS trust can be provisioned with the AWS integration; cluster trust and Kubernetes object collection still need their respective permissions.

For review of the granted access, see [AWS Permissions](/connectors/aws/permissions.md).