Skip to content
AletheiaAletheiaAletheia docs

Resources

The resource list (/resources) is the searchable inventory of everything discovery found.

Searching and filtering

Section titled “Searching and filtering”

Free-text search matches names, identifiers, and ARNs. On top of it you can filter by:

Filter Notes
q Free text across name, native id, and ARN
aws_account_id One connected account
region One region
resource_type Repeatable — several types at once
tag Repeatable — key=value
management_state Repeatable — see mapping
status Live or deleted
stale Resources not seen by the most recent successful scan

Filters are in the URL, so a filtered view is a link you can send to someone.

Filtering by management_state=unmanaged is how you find resources that exist in AWS but are declared nowhere in your code. Read that alongside unmanaged versus unknown before drawing conclusions from the count.

What a resource records

Section titled “What a resource records”

Open any resource for:

  • Identity — account, region, type, native id, ARN, name, tags.
  • Configuration — the resource’s settings as discovery last observed them.
  • Revisions — the history of configuration changes Aletheia has seen, each with what changed.
  • Mapping — which code declares it, with confidence and evidence.
  • Ownership — the application, environment, and owners it belongs to.
  • Dependencies — what it relates to, from the dependency map.
  • Timeline — what changed on it, from the change timeline.
  • Deployments — the pipeline executions that touched it.

Configuration and revisions

Section titled “Configuration and revisions”

Aletheia stores each resource’s configuration and hashes it. When a later scan produces a different hash, that is a new revision, and the difference is what the revision shows.

Values that AWS returns but that are noise — timestamps that move on every read, and similar — are excluded from the hash deliberately. Without that, every resource would appear to change on every scan and the revision history would be worthless.

Sensitive values are redacted before storage.

Deleted and stale resources

Section titled “Deleted and stale resources”

A resource that a scan no longer finds is marked deleted rather than removed. Its history, mapping, and ownership stay readable, because “this existed and then it did not” is usually the interesting part.

Stale is different from deleted: it means the most recent successful scan did not cover this resource — usually because a scan failed for that account or region. A stale resource is not evidence of anything having changed, only of Aletheia not having looked recently.

Supported types

Section titled “Supported types”

Discovery covers a fixed set of resource types. A type Aletheia does not support is not in the inventory and is not an unmanaged finding. See Supported resource types.

Where to go next

Section titled “Where to go next”