> For the complete documentation index, see [llms.txt](https://docs.infraglide.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraglide.com/cloud-sync-and-drift-detection/inventory-discovery.md).

# Cloud Inventory Discovery

## Cloud Inventory Discovery

**Cloud Inventory Discovery** scans your connected AWS, Azure, or GCP accounts to list resources that already exist in the cloud — including resources that InfraGlide may not yet manage. The primary surface is **Operations → Deployed Resources**. ![alt text](/files/R4ymIz8ky8f3L7uKtIl8)

***

### What Inventory Discovery Is For

Use inventory discovery when you need to:

* See live cloud assets for the selected Sandbox and credential.
* Understand what is already running before you design a new pipeline.
* Import selected unmanaged resources into a new InfraGlide pipeline (where provider mappings exist).
* Pair inventory with cost advisor / forecast cards and security scan inputs that read from live or cached inventory signals.

Inventory discovery is complementary to **drift detection**. Drift compares InfraGlide-managed desired configuration to live state. Inventory discovery lists cloud resources whether or not they were created by an InfraGlide pipeline.

### ![alt text](/files/Gl2Sh7IT7Pe1EsjQhOEW)

### Where to Open It

1. Select the target **Workspace / Sandbox** in the header.
2. Open **Operations → Deployed Resources**.
3. Choose the cloud provider and credential when prompted by the page.
4. Refresh or sync to pull the latest inventory for that provider.

The Topology page is a separate multi-pipeline graph view — it does not perform cloud inventory discovery by itself. ![alt text](/files/LfSNhDuf7uOeqCb3GEx2)

***

### How Discovery Works

InfraGlide calls provider-specific inventory services using the credential you select: ![alt text](/files/19Z78iTAB1xUALvs5mOn)

| Provider  | Discovery approach (summary)                        | Examples of asset types surfaced                                                                                                                                   |
| --------- | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **AWS**   | SDK list/describe via the AWS inventory service     | EC2 instances, Lambda functions, S3 buckets, RDS instances                                                                                                         |
| **GCP**   | Cached / Cloud Asset Inventory style resource cache | Compute instances, buckets, Cloud Functions, Cloud Run, Cloud SQL, VPC/subnet, disks, load balancers, Pub/Sub, Firestore, BigQuery, IAM service accounts, and more |
| **Azure** | Azure inventory service list calls                  | Virtual machines, storage accounts, virtual networks, SQL, AKS (as returned by the inventory service)                                                              |

Results can appear both as live API responses in the Deployed Resources UI and as rows in InfraGlide's tracked resource tables when resources are linked to pipelines after deploy or import.

***

### Importing Inventory into a Pipeline

Deployed Resources can create a pipeline from selected inventory items (**Create pipeline**). ![alt text](/files/FdGBj4nWHDsRLNn1GhK4) Behind the scenes InfraGlide maps each cloud `assetType` to a canvas component type and Terraform resource type, then builds designer-ready components (and related synthetic state where needed).

![alt text](/files/jB5u4XxC1FjP2AhtxmVj)

#### Supported import mappings today

**AWS**

* `ec2/instance` → `aws-ec2` / `aws_instance`
* `lambda/function` → `aws-lambda` / `aws_lambda_function`
* `s3/bucket` → `aws-s3` / `aws_s3_bucket`
* `rds/instance` → `aws-rds` / `aws_db_instance`

**GCP** (selected examples)

* Compute Instance, Cloud Storage Bucket, Cloud Functions, Cloud Run Service
* Cloud SQL Instance, VPC Network, Subnetwork, Persistent Disk
* Forwarding Rule (load balancer), Pub/Sub Topic & Subscription
* Firestore Database, BigQuery Dataset & Table
* IAM Service Account, Artifact Registry Repository, Cloud Composer Environment

**Azure**

* Azure inventory items appear under Deployed Resources for discovery and monitoring. Canvas pipeline generation for Azure assets is expanding to support additional resource types.

Unsupported asset types fail with a clear “unsupported asset” style error rather than creating a broken pipeline. ![alt text](/files/IIjFWrcMaCMMIq8uJqt0)

***

### After Import

1. Review the new draft pipeline in the designer.
2. Complete any missing required fields on imported nodes.
3. Attach a credential for that Sandbox.
4. Run **Preview** (`plan`) before **Deploy**.
5. After a successful apply, resources become fully tracked for status badges and drift checks. ![alt text](/files/GutamenRQGVbp8XQ1Y1g) Imported pipelines may retain original Terraform fragments for resources that could not be fully mapped, so regeneration can preserve passthrough blocks where the importer recorded them.

***

### Relationship to Drift Detection

| Capability                      | Inventory discovery         | Drift detection                                 |
| ------------------------------- | --------------------------- | ----------------------------------------------- |
| Primary question                | “What exists in the cloud?” | “Does managed desired config still match live?” |
| Requires prior InfraGlide apply | No                          | Yes (tracked desired config)                    |
| Can create a pipeline           | Yes (AWS/GCP mappings)      | No — syncs config onto an existing pipeline     |
| Writes to cloud                 | No                          | No (deploy still required to change cloud)      |

A practical workflow is: discover unmanaged resources → import a subset into a pipeline → deploy under InfraGlide management → enable drift checks going forward.

***

### Tips and Limits

* Always select the correct Sandbox credential before trusting inventory numbers.
* Org cloud provider policy can hide providers your organization has blocked.
* Inventory coverage is not every possible cloud resource type — only types the provider inventory services list and (for import) types with canvas mappings.
* Cost and security features on Deployed Resources / Security pages may reuse inventory signals; they are documented under Jane AI and Security sections.

***

### See also

* [Real-Time Drift Detection Overview](/cloud-sync-and-drift-detection/overview.md)
* [Cloud Credentials Management](/settings-governance-and-rbac/cloud-credentials.md)
* [Designer Interface Overview](/visual-canvas-and-pipeline-designer/interface-overview.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infraglide.com/cloud-sync-and-drift-detection/inventory-discovery.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.