canonical: https://jentic.com/apis/amazonaws.com/aws-auditmanager

# AWS Audit Manager

AWS Audit Manager automates the collection of evidence for compliance audits across AWS workloads. It uses prebuilt and custom frameworks - such as PCI DSS, HIPAA, and SOC 2 - to map controls to assessable AWS services and continuously gather evidence into structured assessments and reports.

## For AI agents

Use the AWS Audit Manager API to automate compliance evidence collection across AWS workloads on AWS, with 61 operations covering the full control-plane lifecycle.

## Scope

Does not handle vulnerability scanning, threat detection, or remediation actions - use for compliance assessment management and evidence collection only.

## Capabilities

- Create assessments scoped to a framework, accounts, and AWS service set
- Build custom frameworks and controls when prebuilt ones do not match internal policy
- Continuously gather evidence from CloudTrail, AWS Config, Security Hub, and other sources
- Delegate control sets to subject-matter experts for review and approval
- Generate assessment reports that bundle evidence for external auditors
- Manually attach supporting evidence to controls when automated sources are insufficient

## Use cases

### Continuous SOC 2 evidence collection

Run a continuous SOC 2 Type II assessment by selecting the prebuilt SOC 2 framework, scoping it to the relevant AWS accounts, and letting Audit Manager gather evidence from CloudTrail, AWS Config, and Security Hub against each control. Assessment reports compile the evidence on demand for an external auditor. Initial scoping typically takes one to three days; ongoing collection is automatic.

Example prompt: Create an assessment named 'soc2-prod-2026' from the AWS-prebuilt SOC 2 framework scoped to accounts 111111111111 and 222222222222, owned by the security team.

### Custom internal-policy framework

Codify an internal security policy as a custom Audit Manager framework with controls mapped to specific AWS Config rules and CloudTrail event names. Once defined, the framework can be used for repeat assessments quarter after quarter, and Audit Manager replays evidence collection automatically against new accounts joining the scope.

Example prompt: Create a custom framework called 'internal-baseline-v3' containing a control set 'access-controls' with three controls mapped to specific AWS Config rule data sources.

### Auditor handover with packaged reports

Generate an assessment report at the end of a compliance period to hand to an external auditor. Audit Manager packages all collected evidence with metadata about each control's data source so the auditor can trace every claim back to its origin event in CloudTrail or AWS Config. Report generation is on demand, typically minutes per assessment.

Example prompt: Generate an assessment report for assessment id 'a-1234' with the description 'Q2 2026 auditor handover'.

### AI agent driving compliance reviews through Jentic

A compliance agent can run Audit Manager assessments end-to-end by calling its operations through Jentic. It searches for the evidence-collection intents, loads the schemas for CreateAssessment, BatchImportEvidence, and CreateAssessmentReport, and executes them with scoped credentials, so audit-admin keys never enter its context. The agent compresses periodic compliance work to a single intent.

Example prompt: Search Jentic for 'automate evidence collection for a compliance audit', load the CreateAssessment and CreateAssessmentReport schemas, and execute them for the SOC 2 framework on the production accounts.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /assessments | Create an assessment from a framework |
| POST | /assessmentFrameworks | Create a custom assessment framework |
| POST | /controls | Create a custom control |
| POST | /assessments/{assessmentId}/reports | Generate an assessment report |
| POST | /assessments/{assessmentId}/controlSets/{controlSetId}/controls/{controlId}/evidence | Import evidence for a control |
| POST | /assessments/{assessmentId}/delegations | Delegate a control set for review |

## Key resources

- **Assessments** — Active engagements that scope evidence collection across accounts and services
- **AssessmentFrameworks** — Prebuilt or custom control frameworks such as PCI DSS or HIPAA
- **Controls** — Individual control definitions that map to data sources for evidence
- **AssessmentReports** — Generated reports bundling evidence for auditor consumption
- **Delegations** — Workflows that assign control sets to subject-matter experts for review
- **Evidence** — Raw evidence items collected from CloudTrail, Config, Security Hub, and others

## Why Jentic

- **Setup:** Wiring AWS Audit Manager by hand means creating IAM credentials, choosing the right regional host from auditmanager.{region}.amazonaws.com, signing every request with AWS SigV4, and building your own retry and pagination handling. Through Jentic you install once, import AWS Audit Manager from the API Directory, store the AWS access key once, and your agent calls it.
- **Permission scoping:** AWS Audit Manager puts the assessment id in the URL path (/assessments/{assessmentId}/reports, /assessments/{assessmentId}/delegations), so a rule can pin your agent to one assessment: it can generate reports and import evidence for that assessment and nothing else. You choose the operations it may call, so destructive ones like deleting an assessment or a custom control are not included unless you add them.
- **Credential handling:** Your AWS access key for AWS Audit Manager is stored once, encrypted, by your own Jentic One instance and signed with SigV4 at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'automate evidence collection for a compliance audit' or 'generate an assessment report', and Jentic returns the matching AWS Audit Manager operation with its input schema so the agent calls the right endpoint without browsing the AWS service reference.

## Related APIs

- **Security Hub findings** — Security Hub aggregates findings that Audit Manager treats as evidence for several controls
- **CloudTrail event history** — CloudTrail supplies API event evidence that Audit Manager attaches to controls
- **Threat detection** — GuardDuty surfaces threat findings rather than compiling compliance evidence

## FAQ

### What authentication does the AWS Audit Manager API use?

The AWS Audit Manager API uses AWS Signature Version 4 (HMAC) request signing with IAM-issued credentials, the same scheme as every AWS service API. Jentic's your Jentic One instance stores those AWS credentials encrypted in the vault, generates short-lived signed requests at execution time, and never passes raw access keys into the agent's context.

### Can I create a soc 2 assessment for my production accounts with the AWS Audit Manager API?

Yes - the AWS Audit Manager API exposes 61 operations including the actions needed for that scenario. Use the operations listed in the key endpoints section as the starting point, then chain calls as needed for your workflow.

### What are the rate limits for the AWS Audit Manager API?

AWS applies per-account, per-region request rate limits to the AWS Audit Manager control plane. Specific limits are not encoded in the OpenAPI spec; consult the AWS service quotas console for the AWS Audit Manager entry, and design retries with exponential backoff to absorb throttling responses.

### How do I automate evidence collection for a compliance audit through Jentic?

Run pip install jentic, then call client.search('automate evidence collection for a compliance audit') to discover the AWS Audit Manager operations that match. Load the schema for the chosen operation with client.load(...) and execute it with client.execute(...). Jentic handles AWS request signing automatically against the credentials stored in your Jentic One instance.

### Is the AWS Audit Manager API free to call?

AWS does not charge for control-plane API calls themselves on most AWS Audit Manager operations, but the underlying resources you create or operate (fleets, queries, deployments, and so on) incur usage charges according to the AWS Audit Manager pricing page. Refer to the AWS pricing page for the service to estimate cost.

### Which operations should an agent call first when working with the AWS Audit Manager API?

For most workflows, agents should start by listing existing resources to understand the current state, then call the create or update operation that matches the intent. The endpoints listed under Key Endpoints in the catalog give a ranked starting set.

### Can I limit what my agent is allowed to do with the AWS Audit Manager API?

Yes. Because you run Jentic One yourself, your own rules decide which AWS Audit Manager operations and which AWS credentials the agent may use. Since the API carries the assessment id in the URL path, such as /assessments/{assessmentId}/reports and /assessments/{assessmentId}/delegations, you can pin the agent to a single assessment so it only generates reports and imports evidence for that one. You also choose the exact operations it may call, so destructive actions like deleting an assessment or a custom control stay out of reach unless you explicitly add them.
