> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/cloud-scanning/cloud-inventory.md).

# Cloud Inventory

Aikido automatically builds an inventory of every asset across your connected cloud environments. This gives you a single, always up to date view of what exists in your cloud, without needing to check each provider separately.

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2FMevE80pjoW53ZDFgQm3b%2Fimage.png?alt=media&amp;token=9d723ede-4379-438c-ac6e-ef44d7d24829" alt=""><figcaption></figcaption></figure>

## Why it matters

Cloud environments change constantly, and it's easy to lose track of what's actually running across accounts, regions, and providers. Cloud Inventory gives you one place to see every asset, spot exposed or misconfigured resources, and understand how assets connect to each other, without logging into each provider's console.

## What it is

After you [connect a cloud account](/cloud-scanning/connect-your-cloud.md), Aikido pulls in your resources (like EC2 instances, S3 buckets, IAM roles, Lambda functions, and containers running in the cloud) and keeps this list in sync automatically.

{% hint style="info" %}
Aikido also enriches each asset with security context, like vulnerabilities and end of life issues found on VMs and containers. This means the inventory isn't just a list of resources, it's a list of resources with their risk attached.
{% endhint %}

## Viewing your inventory

{% stepper %}
{% step %}

### Go to Clouds

From the left navigation, under Assets, click **Clouds**.
{% endstep %}

{% step %}

### Open a cloud account

Click into the specific cloud account you want to inspect (for example, an AWS account).
{% endstep %}

{% step %}

### Open the Inventory tab

On the cloud account page, click the **Inventory** tab.
{% endstep %}
{% endstepper %}

## Asset map

The map gives you a visual layout of your resources, grouped by region and then by VPC, so you can see what you have and where it lives at a glance.

Each asset appears as a tile with an icon for its type (EC2 instance, RDS database, Kubernetes resource, etc.) and its name. A globe badge with a number means that asset has that many exposure findings, like ports or endpoints open to the internet.

Click a tile to open its details in the panel on the right.

## Node details panel

* **Region and VPC**
* **Auto Scaling group** – name and number of instances in the group (if applicable)
* **Exposure** – investigate the attack graph to see how this asset is reachable (for example, "Reachable via load balancer")
* **Firewall rules** – **Allow Inbound** and **Allow Outbound** rules with protocol, port, and security group
* **Connected resources** – other assets this node connects to and how (for example, a database "via" a security group)
* **View Metadata** – explore the raw resource metadata

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2FNn5hS4Pi4a8HzaJyPrPQ%2Fimage.png?alt=media&amp;token=1110d9b0-7a3e-4d08-8fed-856337f63c52" alt=""><figcaption></figcaption></figure>

Looking to find specific assets instead of browsing? See [Cloud Discovery: Search Asset Inventory](https://help.aikido.dev/cloud-scanning/cloud-discovery-querying-the-asset-graph).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/cloud-scanning/cloud-inventory.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.