Skip to content
AletheiaAletheiaAletheia docs

Quickstart

This takes you from nothing to a populated inventory. Budget about fifteen minutes, plus scan time.

Before you start

Section titled “Before you start”

You need:

  • Permission to create an IAM role in the AWS account you want to connect. The CloudFormation stack Aletheia gives you creates a read-only role and nothing else.
  • An email address to sign up with.

You do not need to change any infrastructure code, install an agent, or open any inbound network access.

1. Create your organization

Section titled “1. Create your organization”

Sign up and choose an organization name. The account you create is the first administrator of that organization; everyone you invite later joins the same organization and sees the same data, filtered by their role.

2. Connect an AWS account

Section titled “2. Connect an AWS account”

Go to the AWS connections screen and start a new connection. Aletheia gives you a CloudFormation template and an external ID unique to your organization.

Deploy the template in the AWS account you want to connect. It creates one IAM role that trusts Aletheia’s account, requires that external ID, and grants read-only access to the resource types Aletheia supports.

Come back and finish the connection. Aletheia validates the role by assuming it. If validation fails, the connection tells you which step failed rather than failing silently.

3. Run your first scan

Section titled “3. Run your first scan”

With the connection validated, trigger a scan. Aletheia walks the supported resource types across your enabled regions and records what it finds.

The first scan is the slowest, because everything is new. It runs in the background — you do not need to keep the page open. Progress is reported per task, so you can see which region or resource type is still running and retry an individual task if one fails.

4. Explore what it found

Section titled “4. Explore what it found”

When the scan completes you have a live inventory. From here you can:

  • Browse and search resources, and open one to see its configuration and revisions.
  • Read the infrastructure overview for the shape of what you run.
  • Group resources into applications and environments, or let inference rules propose groupings from your existing tags.

5. Connect your code

Section titled “5. Connect your code”

Discovery tells you what exists. To find out which code declares it, connect a repository and point Aletheia at your Terraform state. See Connect your code.

This is the step that turns the inventory into a control plane: once mapping runs, every resource carries a management state and, where Aletheia found one, a link to the code that declares it.

Where to go next

Section titled “Where to go next”