Explore your infrastructure

Once discovery and mapping have run, the inventory is something you can ask questions of.

The surfaces

Overview gives you the shape of what you run: how much of it there is, how much is managed by code, and what changed recently.

Resources is the searchable inventory. Filter by account, region, type, tag, or management state, and open any resource to see its configuration, its revisions, its owners, and the code that declares it. To see one application’s or environment’s resources, open it from the application itself.

Applications, environments and teams are how you group resources into the units your organization actually thinks in. Memberships can be declared by hand or proposed by inference rules from your existing tags — and an inferred membership stays visibly inferred until someone confirms it.

Dependency map shows how resources relate to one another, so you can see what a change would touch before making it.

Change timeline merges what changed in AWS with what your pipelines reported, which is what surfaces changes made outside any pipeline.

In this section

• Infrastructure overview — the landing page, its tiles, and how to read freshness.
• Resources — searching and filtering the inventory.
• Applications, environments and ownership — grouping resources, and how inference rules are written and previewed.
• Dependency map — the typed relationship graph and its evidence.
• Change timeline — what changed, and whether a pipeline did it.

Where to go next

• Ask Aletheia to query all of this in plain language.
• API to reach the same data from your own tools.