ato-source-aws

Collects read-only AWS compliance evidence and exports redacted JSON artifacts per service and region.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/AI-Strategy-LLC/AgentSkills --skill ato-source-aws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ato-source-aws
Source: https://github.com/AI-Strategy-LLC/AgentSkills/tree/main/skills/repo-scope/ato-source-aws
Command: npx skills add https://github.com/AI-Strategy-LLC/AgentSkills --skill ato-source-aws

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sibling of ato-artifact-collector. Collects NIST 800-53 evidence from AWS via the mcp__AWS_API_MCP_Server__call_aws MCP tool. Invoked by the orchestrator when AWS scope is configured. Strictly read-only, ambient-auth, US-region-only, scope-confirmed. Do not invoke directly unless running an ATO collection.

Core Features & Use Cases

  • Read-only AWS scope validation and auth probe to verify access aligns with the declared accounts and regions.
  • Per-service discovery using the AWS CLI cheatsheet to enumerate evidence and export JSON artifacts, with redaction and console links.
  • Generates a citation batch and supports guardrails for scope confirmation, non-US region handling, and auth failures.

Quick Start

Run the ato-source-aws workflow to begin collecting read-only AWS evidence and exporting findings.

Frequently Asked Questions about ato-source-aws

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect AWS evidence for NIST 800-53 compliance without making changes to my environment?

AWS evidence collection for NIST 800-53 compliance is performed in read-only mode to enumerate accounts and regions without making changes. It uses ambient authentication to probe access and exports redacted JSON artifacts.

Can I run AWS compliance evidence collection outside of US regions?

AWS compliance evidence collection enforces hard rules for US regions only. The process applies guardrails for non-US region handling and will refuse to operate outside the declared US regional scope.

How are credentials and secrets handled during AWS scope discovery?

Credentials and secrets are handled safely during AWS scope discovery by refusing write operations and redacting all sensitive data. The exported JSON artifacts only contain redacted evidence and console links.

Does AWS evidence collection support ambient authentication for read-only discovery?

AWS evidence collection uses ambient authentication to perform read-only discovery against defined accounts and regions. An auth probe verifies that access aligns with the declared AWS scope before enumerating services.

What is the best way to generate a citation batch from AWS compliance findings?

Generating a citation batch from AWS compliance findings is done by running read-only per-service discovery using the AWS CLI cheatsheet. This process exports findings as redacted JSON artifacts alongside the citation batch.

Do I need to configure an AWS scope before collecting NIST 800-53 evidence?

An AWS scope must be configured before collecting NIST 800-53 evidence. Scope confirmation is a required guardrail, ensuring the auth probe and per-service discovery target the correct declared accounts and regions.