# SOC 2 with AI on AWS

> SOC 2 AWS evidence by service area, what AWS covers and what you do, and prompts to prepare with an AI assistant. CPA firm audit from $4,400, no platform.

- Canonical: https://auditsuisse.com/soc-2-with-ai-on-aws
- Language: en
- Author: Sébastien Ruosch, CPA — Director of Audits
- Published: 2026-11-15
- Updated: 2026-11-15
- Alternates: fr → https://auditsuisse.com/fr/soc-2-avec-l-ia-sur-aws, es → https://auditsuisse.com/es/soc-2-con-ia-en-aws

SOC 2 on your stack

 The short answer

SOC 2 evidence on AWS is a set of exports and configuration listings from your own accounts: identity and access, logging, encryption, network, backups and deployments. Each one states its source, the command or query, the date and the record count. An AI assistant can write the read-only commands; your team runs and checks them. AWS is a subservice organization in your report, and a licensed CPA firm examines what you provide.

## Key takeaways

- The auditor works from populations and configuration listings pulled from the AWS API.
- Every artifact carries four facts: source (account and region), command or query, date and record count.
- The assistant writes list and describe commands. A person runs them under a read-only role, reviews the output and sends it unedited.
- This is AI-guided preparation, CPA-performed audit. Software never forms the opinion.

## What evidence does a SOC 2 auditor ask for on AWS?

Your auditor’s request list sets the exact items; these are the types. The general method is in [collect SOC 2 evidence with an AI agent](https://auditsuisse.com/soc-2-evidence-collection-with-ai-agents).

SOC 2 evidence on AWS by service area: where the evidence lives and the artifact an auditor asks for.

| Service area | AWS services | Artifact an auditor asks for |
| --- | --- | --- |
| Identity and access | AWS IAM, IAM Identity Center, AWS Organizations | The IAM credential report (users, MFA status, access key age) and the listing of roles with attached policies. For selected joiners and leavers, the request and the date access changed. |
| Logging and monitoring | AWS CloudTrail, Amazon CloudWatch, Amazon GuardDuty | The trail configuration (regions, log destination, log file validation), the alarm list, GuardDuty status per account and region, and the period’s findings with the ticket for each. |
| Encryption and key management | AWS KMS; encryption settings of Amazon S3, EBS and RDS | The listing of KMS keys with rotation status, and the listing of buckets, volumes and databases with their encryption setting. |
| Network | Security groups and network ACLs in Amazon VPC, AWS WAF, AWS Config | The listing of security group rules, with those open to any address marked, the list of public endpoints, and AWS Config rule results. |
| Backups and recovery | AWS Backup, RDS automated backups, S3 versioning | Backup plans and retention settings, the period’s backup job history, and the record of a restore test (what, when, by whom, result). |
| Change and deployment | AWS CloudFormation or Terraform, your pipeline, AWS Config, CloudTrail | The population of production deployments for the period. For selected changes, the pull request, review and approval. CloudTrail events for console changes. |

Most of it supports CC6 Logical and Physical Access Controls, CC7 System Operations and CC8 Change Management: see the [SOC 2 controls list](https://auditsuisse.com/soc-2-controls-list-by-trust-services-criteria).

## What does AWS cover, and what do we still have to evidence?

Under the shared responsibility model that AWS describes, AWS is responsible for the infrastructure that runs its services. You are responsible for what you configure and run on them: identities, network rules, encryption settings, logging, backups and your code. The more managed the service, the more AWS operates. Read [AWS’s page on the shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) for the split, and [SOC 2 on AWS and Azure](https://auditsuisse.com/soc-2-on-aws-and-azure) for what stays with you.

In your report, AWS is a subservice organization, normally carved out. Your description names AWS and the services you use. See [subservice organizations: carve-out vs inclusive](https://auditsuisse.com/subservice-organizations-carve-out-vs-inclusive) and [vendor management for SOC 2](https://auditsuisse.com/vendor-management-for-soc-2-compliance).

## Which AWS accounts and regions does each export have to cover?

An export is useful only if the auditor can tell that it is complete. On AWS that means accounts and regions. IAM is global to an account, but most services answer per region, so a GuardDuty or security group listing from one region says nothing about the others. Start from the accounts in scope (see [how to scope systems for SOC 2](https://auditsuisse.com/how-to-scope-systems-for-soc-2)) and run each command in every account and every enabled region.

Keep the raw output as returned. Auditors test such listings for completeness and accuracy before relying on them: see [tests of controls, IPE and IUC](https://auditsuisse.com/tests-of-controls-ipe-iuc) and [audit evidence management best practices](https://auditsuisse.com/audit-evidence-management-best-practices).

## Which prompts write read-only AWS commands for these exports?

Run the commands yourself under a role that can only read. AWS publishes managed policies for this, such as SecurityAudit. Before you paste output into an assistant, read [is it safe to put security documents into ChatGPT or Claude](https://auditsuisse.com/is-it-safe-to-use-ai-for-soc-2).

### Prompt: read-only AWS CLI commands by service area

```
You are helping my team prepare SOC 2 evidence from our AWS accounts. I will run every command myself under a read-only role.

Ask me first which accounts and regions are in scope, whether we use AWS Organizations and IAM Identity Center, and how our people sign in today. Wait for my answers.

Then write AWS CLI commands for these listings: IAM users, roles and MFA status; CloudTrail trails; GuardDuty detectors; KMS keys and rotation status; security group rules; backup plans and jobs. Use only list, get and describe operations. Never write a command that changes configuration.

Each command saves its raw output, unedited, to a file with a header: source (account ID and region), the exact command, date and time in UTC, and record count.

Mark every assumption as [ASSUMPTION].
List anything you assumed that I need to verify.
```

### Prompt: a query for changes made in the console

```
I need the population of configuration changes made in the AWS console, outside our pipeline, during our SOC 2 period.

Ask me where our CloudTrail logs are stored, which tool we query them with today, the period, and how our pipeline identifies itself in the logs. Wait for my answers.

Then write one read-only query that returns write events not made by the pipeline role: time, account, region, principal, event name, resource. Tell me how to record the query text, the run date and the row count with the result.

Do not interpret, edit or add to the result; a person on my team decides what each change means. Mark every assumption as [ASSUMPTION].
List anything you assumed that I need to verify.
```

### Prompt: check an export before a person signs it off

```
I will give you the header of an AWS export (source, command, date, record count) and its column names, not the full output.

Ask me which accounts and regions the population should cover and how the command was run.

Then list what a reviewer should check: missing accounts or regions, filters or pagination that could drop records, a count that differs from the console. Do not edit the output, fill gaps, or create or alter evidence. Mark every assumption as [ASSUMPTION].
List anything you assumed that I need to verify.
```

AI-written policies and descriptions are acceptable only if they describe what your company actually does. The audit tests how controls operate, not how documents read. See [what auditors accept from AI](https://auditsuisse.com/what-auditors-accept-from-ai).

## Who does what

Auditsuisse explains the criteria and sends its evidence request list once engaged. Your management designs and operates the controls; the firm does not configure your AWS accounts or choose your controls.

Who does what when you prepare SOC 2 evidence on AWS.

| Task | Your team (with or without AI) | Your AI assistant | The auditor |
| --- | --- | --- | --- |
| Write export commands | Reviews each command before it runs | Drafts list and describe commands with the header for each output | No role |
| Run the exports | Runs them under a read-only role and keeps the raw output | Needs no access to your accounts | Requests the populations and listings on the evidence request list |
| Check completeness | Confirms every account and region is covered | Points out filters and missing regions for a person to resolve | Tests that each listing is complete and accurate before relying on it |
| Change a setting | Decides and makes the change | Explains the setting and its options | No role |
| Reach a conclusion | Signs the management assertion | None | Selects items from each population, inspects the record behind each one and forms the opinion |

## Zero-Platform SOC 2 Audit: the fee

A Zero-Platform SOC 2 audit from Auditsuisse costs $4,400 for Type I and $5,500 for Type II for companies of up to 50 people, fixed fee, Security criteria.

No compliance platform is required, so you save the platform fees, which start at about $10,000 to $15,000 a year for a GRC platform (an illustrative figure, not any vendor’s price).

Zero-Platform SOC 2 Audit fees for companies with 1–50 employees (USD, fixed fee, Security Trust Services Category). Fees as of November 15, 2026.

| Company headcount | SOC 2 Type I | SOC 2 Type II | Type I + Type II (combined) |
| --- | --- | --- | --- |
| 1–50 employees | $4,400 | $5,500 | $7,700 |

[See all headcount tiers](https://auditsuisse.com/zero-platform-soc-2-audit#fees)

Fees as of November 15, 2026.

## Free kit: prepare for SOC 2 without a platform

The prompt library from these guides, a policy index, the gap-assessment scoring sheet, the risk register template and the cost worksheet, as CSV and Markdown, with a short guide to the workflow. Free to use with attribution; not a substitute for an examination. Our evidence request list is not part of the kit: you receive it once the engagement letter is signed.

## Frequently asked questions

### Can Claude Code or another agent run the AWS commands for us?

It can, if its role can only read and a person reviews every command and output before anything is sent. Either way, the evidence is the raw output with its source, command, date and count.

### Do we need a compliance platform to collect AWS evidence?

No. A platform connects to AWS and collects these listings continuously. Without one, you run the exports and send them to the auditor. The [Zero-Platform SOC 2 audit](https://auditsuisse.com/zero-platform-soc-2-audit) is built for that, and the [guide to SOC 2 with AI](https://auditsuisse.com/soc-2-with-ai) covers the rest of the preparation.

### Will Auditsuisse run the commands or review our AWS setup before the audit?

No. We request evidence and examine it. Preparing the environment and collecting evidence is your team’s work. Hands-on help comes from a separate provider.

## Sources & further reading

AICPA, [2017 Trust Services Criteria (with revised points of focus, 2022)](https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022); SSAE No. 18, AT-C sections 105 and 205. Amazon Web Services, [Shared Responsibility Model](https://aws.amazon.com/compliance/shared-responsibility-model/).

**Related:** [SOC 2 with AI on Google Cloud](https://auditsuisse.com/soc-2-with-ai-on-google-cloud), [SOC 2 with AI on Azure](https://auditsuisse.com/soc-2-with-ai-on-azure), [SOC 2 on AWS and Azure](https://auditsuisse.com/soc-2-on-aws-and-azure).

Product names are trademarks of their owners. Auditsuisse is not affiliated with these vendors.

---
Source: https://auditsuisse.com/soc-2-with-ai-on-aws · This Markdown edition is generated from the same content as the HTML page.
