> For AI agents: the complete documentation index is available at https://www.jumpserver.com/docs/llms.txt, the full documentation bundle is available at https://www.jumpserver.com/docs/llms-full.txt.

# Cloud Sync


Enterprise Edition

**Cloud Sync** requires JumpServer Enterprise Edition. The menu entry is hidden when the license is missing or the account lacks cloud sync permissions.

[Request 14-day free trial](https://www.jumpserver.com/free-trial)

**Cloud Sync** imports hosts and database instances from cloud platforms and
keeps the JumpServer asset inventory in step with the instances that actually
exist. A cloud account stores the platform credentials and the sync task settings,
a sync policy decides which instances are imported, and the synchronize instance
tab shows what the last run produced.

Open the page from **Console > Assets > Hosts > Cloud Sync**. The page title is
**Host - Cloud sync**; the same feature is available for database instances with
the **Database** category.

![Figure 1: Hosts tab with the Cloud Sync entry point.](/images/v5/jumpserver/v5_admin_assets_06.png)

## Overview

The page has three tabs:

| Tab                  | Purpose                                                                                                                                            |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Accounts             | Cloud platform accounts: provider, credentials, region, and the sync task settings for each account.                                               |
| Sync policy          | Ordered rules that decide which instances are imported or skipped and which actions apply. A built-in default policy exists and cannot be deleted. |
| Synchronize instance | The result of sync runs: instances that were discovered, imported, or skipped.                                                                     |

## Before you begin

- Sign in with an account that can manage assets and cloud sync.
- Have credentials for the cloud platform, and make sure JumpServer can reach the
  platform API endpoint.
- Decide which regions and instances should be imported, and which node in the
  asset tree should receive them.


Note

Until a cloud account is configured, the **Synchronize instance** tab stays
empty. Create the account first, then review the policy, then run the sync.

## Create a cloud account


1

Open the **Accounts** tab and click **Create**.

2

Select the provider in the wizard and click **Next**.

3

In the **Authentication** step, enter the credentials and region details.

4

In the **Sync** step, select the instances to import and the node that should
receive them, then review the **Result** step and submit.

![Figure 2: Create cloud account for a cloud platform.](/images/v5/jumpserver/v5_admin_assets_07.png)

After the account is created, open it to adjust the sync task: the source IP type
(public or private), whether released instances are removed from the inventory,
whether existing assets are always updated, and the sync **Timer** (periodic
interval or crontab). The account detail also shows the sync policy relation.

## Work with sync policies

A sync policy is an ordered set of rules. Each policy has a name, a priority,
rules that match instances, actions applied to matched instances, and a rule
relation (all or any). Lower priority values are evaluated earlier. Keep
policies narrow: one policy per platform or region is easier to troubleshoot than
a single policy that spans many environments.


1

Open the **Sync policy** tab and click **Create**.

2

In **Create sync policy**, enter a **Name** and **Priority**.

3

Add the rules and actions, choose the rule relation, then click **Submit**.

## Review sync results


1

Run the sync, or wait for the scheduled run to start.

2

Open the **Synchronize instance** tab to review the discovered instances and
their status.

3

Return to the **Hosts** tab of the asset list and confirm that the expected hosts
now appear.

Synced hosts become normal assets: they can be added to nodes, bound to accounts,
and authorized like manually created assets. If a host does not appear, check the
policy rules first, then the account's connection state, and finally whether the
instance already exists under a different address.

## Related topics

- [Assets](https://www.jumpserver.com/docs/features/console/assets/index.md)
- [Zones](https://www.jumpserver.com/docs/features/console/assets/zones.md)
- [Accounts](https://www.jumpserver.com/docs/features/console/accounts/index.md)
- [PAM accounts](https://www.jumpserver.com/docs/features/pam/accounts.md)