Skip to content

Changelog

Release notes are published here with each release.

  • Environment variables that hold a bare name, such as TABLE_NAME=orders (what CloudFormation Ref returns), now link a Lambda function or ECS task definition to the DynamoDB table, S3 bucket, SQS queue, SNS topic, Kinesis stream or Lambda function of that name, as an inferred relationship. Only when exactly one resource in the scan has the name; the value is still never stored
  • resources show: more than 25 relationships of the same kind (a CloudFormation stack’s manages, for example) are counted in relationships.summarized instead of listed, with the command that lists them. A stack’s output in our measurement went from 64 KB to 30 KB
  • resources show by ID also lists other resources that only share that name (alsoNamed)
  • impact on a KMS alias points at the key it names (aliasOf)
  • Fewer unresolved relationships: a stack no longer links to parts of other resources (routes, security group rules, resource policies, …); WAFv2 and scalable targets in stacks, target tracking alarms → scaling policies, Step Functions and DynamoDB alarms, and Lambda custom log groups now resolve
  • A request rejected because the computer’s clock was off (for example after sleep) is reported as invalid_credentials, not access_denied. A region without EFS replication is no longer a failed unit
  • Usage statistics: wait up to 3 seconds (instead of 1) for the send at the end of a command. The first request after the API has been idle could take over a second, and events that had already been stored were sent again on the next run. Usually the send still takes under a second
  • Fix the links in the README on the npm page: the link to the Japanese README and the links to documents no longer return 404. They now point to this website (the CLI itself is unchanged)
  • Read-only scans of 76 plugins covering about 390 resource types
  • Coverage, evidence and confidence for every fact
  • awnexa overview: the entry points and what sits behind them, in one call
  • Relationship graph, impact analysis and snapshot diffs (by default, the latest scan against the previous one)
  • Refer to resources by uid, ARN, ID or name; filter lists by property values (resources list --where), and empty or short lists say why (resultCoverage)
  • Optional usage summary: daily values of a few CloudWatch metrics for the last 14 days (scan --metrics)
  • Try it without AWS: awnexa init --sample creates sample data of a made-up system
  • MCP server and Claude Code Skills, also as a Claude Code plugin (Claude Code)
  • Markdown design documents with Mermaid diagrams
  • Free: one AWS account per data directory, diffs between the 3 newest snapshots (Pricing)
  • Works behind HTTP(S) proxies, including TLS-inspecting ones (Configuration)
  • Anonymous usage statistics are on by default: the first run tells you and sends nothing, and awnexa telemetry disable or AWNEXA_TELEMETRY=0 turns them off (Data the CLI sends)