Use cases
Each example shows what you ask, what Claude Code looks up in Awnexa, and what a good answer looks
like. The account, names and IDs are made up: they are the sample data that
awnexa init --sample creates, so you can try the
same questions without AWS. The Skills installed with awnexa skills install
cover these tasks, so you can ask in plain words.
Every answer starts from the same check: Claude Code reads awnexa status and the coverage first,
so it knows how old the data is and what was not collected.
awnexa status --compactawnexa coverage --status partial,failed,access_denied,unsupported,unknown --compactExplain the system and draw a diagram
Section titled “Explain the system and draw a diagram”You: Explain this AWS environment and draw an architecture diagram.
Claude Code gets the whole picture in one call, then the details it needs:
awnexa overview --compactawnexa resources show orders-db --fields Engine,MultiAZ,StorageEncrypted --compactClaude Code: From Awnexa (scan of 2026-10-06 10:42; RDS in ap-northeast-3 was access denied and two S3 buckets’ encryption settings could not be read): there are three public entry points. The ALB
alb-webforwards HTTPS through the target groupweb-tgto the ECS servicewebin the subnetsorders-app-aandorders-app-c. The HTTP APIorders-apiinvokes three Lambda functions (orders-create,orders-get,checkout). The EC2 instanceorders-bastionhas a public IP address. Security groups allow the compute on these paths to reach the Aurora clusterorders-dband the RDS instancereporting— a permission, not observed traffic. The role of the three functions is allowed to send to the SQS queueorders-events, and the task role ofwebto read the bucketorders-assets-111122223333. The environment variables ofcheckoutnameorders-eventsandorders-db, those oforders-createnameorders-events, and those ofwebandorders-workername the bucketorders-assets-111122223333(inferred from the configuration). Separately, the functionorders-workerreadsorders-events, whose failed messages go toorders-events-dlq. (Mermaid diagram follows.)Not checked: RDS in ap-northeast-3: databases there may exist but were not visible to this scan. Whether the code really uses these permissions and variables is not part of the configuration; the AWS managed policy of the functions’ role was not evaluated.
The aws-architecture Skill also writes design documents
from awnexa report, keeping the coverage warnings.
Check the impact of a change
Section titled “Check the impact of a change”You: What breaks if I delete security group
sg-0a1b2c3d4e5f60718?
awnexa impact sg-0a1b2c3d4e5f60718 --depth 3 --compactClaude Code: From Awnexa: 8 resources use this security group (
orders-app) directly: the ECS serviceweb, 2 network interfaces, the Lambda functioncheckout, the Aurora clusterorders-dband its 2 instances, and the Secrets Manager VPC endpointorders-secrets-endpoint. The security groupsorders-dbandreporting-dballow inbound traffic from it andalb-weballows outbound traffic to it, so their rules depend on it too. Through these, the ALBalb-web, the APIorders-apiand the RDS instancereportingare affected further away.Limits: only references in the scanned services are visible. An application that connects by IP address, or a resource in a service Awnexa does not support yet, would not appear here.
Investigate an incident
Section titled “Investigate an incident”You: Checkout has been failing since this morning. What is connected to the
checkoutfunction, and what changed recently?
awnexa graph checkout --depth 2 --compactawnexa snapshot list --compactawnexa snapshot diff --compactWithout scan IDs, snapshot diff compares the latest scan with the one before it. To compare
other scans, give two scan IDs from snapshot list.
Claude Code: From Awnexa: between yesterday’s and today’s scans, two resources changed. The Lambda function
checkoutrenamed its environment variables (DB_HOSTandDB_NAMEbecameDATABASE_HOSTandDATABASE_NAME, andPAYMENT_TIMEOUT_MSwas added; the values are masked) and gained a second security group,orders-app. The security groupsg-checkoutlost its outbound rule to the database subnets (TCP 5432).My reading (not a fact from the scan): the removed rule alone does not cut
checkoutoff fromorders-db: the addedorders-appgroup allows all outbound traffic, andorders-dballows inbound traffic from it. The renamed variables are the more likely cause: if the code still readsDB_HOST, it gets no database address. Check the function’s logs and the deployed code.
Awnexa provides the changes and the connections; finding the cause is Claude Code’s reasoning, and it says so.
Review the configuration
Section titled “Review the configuration”You: Which resources are publicly reachable or unencrypted?
awnexa resources list --type AWS::RDS::DBInstance --fields PubliclyAccessible,StorageEncrypted --compactawnexa resources list --type AWS::EC2::SecurityGroup --fields IpPermissions --limit 100 --compactawnexa resources list --type AWS::S3::Bucket --fields PublicAccessBlockConfiguration,ServerSideEncryptionConfiguration,UnretrievedConfigurations --compactClaude Code: From Awnexa: one RDS instance
reportinghasPubliclyAccessible: true; all three RDS instances in ap-northeast-1 are encrypted. Security groupsg-bastionallows TCP 22 from0.0.0.0/0— a rule that allows traffic, not proof that anyone connected.alb-weballows TCP 443 from0.0.0.0/0, as expected for a public load balancer. S3: all three buckets block public access.Not checked: RDS in ap-northeast-3 was access denied (
resultCoverage), so instances there are unknown. The encryption settings oforders-logs-111122223333andorders-exports-111122223333could not be read (UnretrievedConfigurations), so they are unknown, not unencrypted.
Bring resources under IaC
Section titled “Bring resources under IaC”You: Write Terraform for this VPC and its subnets.
awnexa resources list --type AWS::EC2::VPC --compactawnexa resources list --parent vpc-0123456789abcdef0 --compactawnexa resources show vpc-0123456789abcdef0 --full --compactClaude Code writes the Terraform from the collected properties and notes values it could not see, for example secrets that Awnexa masks.
Write operations documents
Section titled “Write operations documents”You: Draft a runbook for this system.
awnexa overview --compactawnexa report --out ./docs/aws --doc overview,network,securityClaude Code drafts the inventory, dependencies, routine checks and first steps for common failures, and marks the parts that depend on what was not collected.
Questions you can paste
Section titled “Questions you can paste”Understand
- “Explain this AWS environment and draw an architecture diagram.”
- “Summarize the VPCs, their subnets and how they connect to the internet.”
- “What sits behind this load balancer?”
- “Which resources belong to the
orderssystem (tagapp=orders)?”
Change safely
- “What depends on this security group? What breaks if I delete it?”
- “Is it safe to delete this subnet?”
- “Which Lambda functions use this IAM role?”
Investigate
- “What changed since last week’s scan?”
- “Show what is connected to the
checkoutfunction and what changed in it recently.”
Review
- “Which resources are publicly reachable or unencrypted?”
- “Review the security groups that allow traffic from the internet.”
- “Which services could not be scanned, and why?”
Document and automate
- “Turn the current network setup into Terraform.”
- “Draft a runbook for this system.”
- “Write a design document for this account.”