---
title: "Add and scan your first nodes"
description: "Add nodes one at a time, in bulk or through an integration, then scan them."
product: "Guardian"
edition: "Classic"
type: "get-started"
url: "https://docs.cloudhouse.com/guardian/classic/getting-started/add-and-scan-nodes/"
---
# Add and scan your first nodes

Stage 3 of [getting started](https://docs.cloudhouse.com/guardian/classic/getting-started/index.md). With scanning services, service accounts and firewalls in place, add the nodes you want Guardian to watch and scan them for the first time.

Applies to: `Guardian Classic`

## Add nodes

**Inventory** > **Add Nodes** brings every way of adding nodes into one place: see [Add Nodes](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-nodes/index.md).

[Add nodes in bulk](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-nodes-in-bulk/add-nodes-in-bulk/index.md)
:   Connect to a source such as AWS, Azure or GCP, choose the node types to import, and send them to [Detected](https://docs.cloudhouse.com/guardian/classic/inventory/detected/detected/index.md) to review later or [Monitored](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/monitored/index.md) to scan straight away. Bulk adds always go through a Connection Manager.

[Add a single node](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/add-a-single-node/index.md)
:   Add one node at a time from any of the 27 supported categories, using the connection the source requires.

!!! tip "Using AWS?"
    [Get started with Guardian and AWS](https://docs.cloudhouse.com/guardian/classic/getting-started/aws-getting-started/index.md) walks through connecting AWS and choosing which instances to monitor.

## Keep nodes in step with an integration

An [integration](https://docs.cloudhouse.com/guardian/classic/control/integrations/integrations/index.md) connects Guardian to a source once and then keeps your nodes in step with it on a schedule, so you don't have to re-import or schedule a [node sync job](https://docs.cloudhouse.com/guardian/classic/control/job-schedule/job-types/synchronize-nodes-job-type/index.md). Integrations can also run [actions](https://docs.cloudhouse.com/guardian/classic/control/events/actions/actions/index.md) when events happen, such as posting to Slack when a scan fails.

## Scan your nodes

Every scan records a node's whole configuration, so regular scans are what let you compare systems and see how one has changed over time. Results appear on [Node Scan Results](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/nodes/node-scan-results/index.md). You can scan by hand or on a schedule: see [Scan Nodes](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/scan-options/scan-nodes/index.md) and [Scan job type](https://docs.cloudhouse.com/guardian/classic/control/job-schedule/job-types/scan-job-type/index.md).

## Next

- [*Explore* **Where next** Node groups, policies, reports and more.](https://docs.cloudhouse.com/guardian/classic/getting-started/index.md#next-features)
- [*Learn* **Guardian concepts** How the parts of Guardian fit together.](https://docs.cloudhouse.com/guardian/classic/getting-started/concepts/index.md)