Skip to content

Security overview

A one-page summary for teams that review Awnexa before using it. Each point says how it is enforced. To report a vulnerability, see Security.

A command-line tool that runs on your machine or CI runner. It reads AWS configuration with your credentials, saves it in a local SQLite database, and answers queries from that database (CLI and a stdio MCP server for Claude Code). There is no Awnexa server that stores your data.

  • Only Describe*, List*, Get*, BatchGet* and Search* APIs. A test checks every AWS SDK command the source imports, so a change that adds another kind of call fails the build.
  • APIs whose names look read-only but return values, logs or credentials are forbidden one by one and checked by the same test, for example GetSecretValue, GetParameter, GetLogEvents, LookupEvents, GetRecords and Lambda’s GetFunction (which returns a link to the code).
  • Secrets Manager, SSM Parameter Store and KMS: metadata only, never the values. No S3 object listings or contents, no DynamoDB items, no log events, no Kubernetes API.
  • No endpoint overrides: requests go to the AWS endpoints the SDK chooses.
  • awnexa plugins lists the APIs each plugin calls and the IAM actions they need.

Recommended IAM setup: a role with only the AWS managed policy ReadOnlyAccess. Awnexa does not need anything that changes AWS. An optional deny policy for data reads (S3 objects, secret values, log events and similar) is in the getting started guide.

  • Resolved by the AWS SDK’s default credential chain (profiles, SSO, environment variables, roles). Awnexa saves only the profile name and the ARN of the identity that scanned, never keys or tokens.
  • Not written to the database, logs, error messages or evidence files. Log output redacts credential fields.
  • One exception: a proxy URL with user:password can be saved in config.json (file mode 600). It is masked whenever it is displayed or logged.

Everything stays in the data directory (.awnexa by default): the database, config.json and evidence files (the sanitized API responses each fact came from).

  • Before saving, values under keys such as Password, Secret, Token and PrivateKey, access keys and PEM private keys are replaced with [REDACTED]. Environment variable values of Lambda functions and ECS task definitions are replaced too (the variable names are kept).
  • The directory is created with mode 700 and the files with mode 600 on Linux and macOS, and it has a .gitignore so it is not committed by mistake. On Windows, keep it in your user profile.
  • Names, IDs, CIDR ranges, tags and policies are kept, because they are the configuration. Treat the data directory as you would treat your infrastructure documentation.
  • Deleting is local only: awnexa snapshot prune (with confirmation and --dry-run).
  • AWS API endpoints, for scans.
  • Awnexa’s own backend (api.awnexa.net), only for anonymous usage statistics. They are on by default; the first run says so and sends nothing, and awnexa telemetry disable or AWNEXA_TELEMETRY=0 turns them off. They never include AWS configuration data, account IDs, credentials, file paths or host names. The full list of fields is in Data the CLI sends, and with AWNEXA_TELEMETRY=debug the CLI prints the events instead of sending them.
  • Nothing else. HTTP(S) proxies only relay the connections; TLS goes through to AWS and to the backend.
  • awnexa mcp uses stdio only: it opens no network port and does not call AWS.
  • Installed from npm. No runtime dependency runs an install script, and the SQLite driver uses prebuilt binaries included in its package, so installation downloads and builds nothing else.
  • The source repository is not public yet, so packages are published without npm provenance.

Resource names, tags, descriptions and policies can be written by anyone who can change your AWS account, so they could carry text meant to instruct an AI. Awnexa does not change these values (they are the facts), but its MCP server instructions and Skills tell Claude Code to treat them as data, never as instructions, and to report values that read like instructions. Awnexa’s tools are read-only and never call AWS, so such text cannot change AWS through Awnexa. Other tools Claude Code may have, such as a shell or the AWS CLI, are outside Awnexa; keep commands that change AWS behind Claude Code’s permission prompts.

  • Change AWS resources, or read data inside them (objects, items, messages, logs, secret values).
  • Run as a service or keep your data anywhere but your data directory.
  • Send AWS configuration data anywhere.