Cloud Import Agent

Convert your cloud infrastructure into a reusable blueprint

Overview

The Cloud Import Agent turns unmanaged cloud resources into a fully managed Bluebricks environment. You select the resources that define your environment, and the agent codifies them into a reusable Blueprint, validates the generated configuration, and iterates until the plan reaches a no changes state. This ensures the code fully reflects your current cloud setup and is stable for automation.

During the process, the agent:

• Generates infrastructure code from the selected resources

• Validates the generated configuration

• Iterates until the plan reaches a no-changes state

At this point, your environment is stable and automation-ready. When the process completes successfully, the new environment appears in the Cloud Graph. From there, you can automate, govern, and evolve it using the Bluebricks orchestrator.

Prerequisites

Before you start, ensure:

• A Collection is connected to your cloud account

• The Collection has both:

  • Discovery permissions

  • Orchestration permissions

Without both permission sets, the agent cannot analyze existing resources or execute the generated Blueprint.

How to import using the Bluebricks agent

1. Open the cloud graph

2. Select a collection with orchestration and discovery icons

3. In the explorer drawer, select one or more unmanaged resources

4. Add an environment name

5. Click Import

After the task begins:

• The drawer automatically switches to the agent tab

• The agent will codify the selected resources

  • The code is tested and iterated until no changes are detected

• The agent will publish the blueprint and create the environment

After the task is completed successfully:

• A link to the run plan page will be displayed within the agent tab

• The generated blueprint appears in the blueprints list

• The created environment appears in the environments list

• The cloud graph refreshes with the new managed nodes

Choosing what to import (single- vs. multi-resource)

Before starting import, consider whether you want to manage one resource independently or import a complete set of dependent resources together. This choice impacts how reusable and maintainable the generated code and blueprint will be.

Single-resource import

Use this flow when importing a standalone resource such as a database, load balancer, or storage bucket which is not yet managed by code.

Multi-resource import

Select multiple related resources to codify them into a single environment, preserving their dependencies and relationships—making them into a single deployable unit.

Note: Selecting unrelated resources may fail the import due to cross-resource dependencies. We recommend grouping resources that belong to the same group or represent a self-contained infrastructure environment.

Best practices

• Import logically related resources together, for example resources that comprise a specific environment or a self-contained part of one environment

• Use clear and descriptive environment names

• Review generated blueprints before applying further changes

• Create smaller, focused blueprints over large, monolithic ones

Reviewing the generated code

After a successful import, you can retrieve the full Terraform code locally using the bricks CLI:

bricks bp fetch

This applies to both manually published packages and codified resources. Once fetched, you can review, modify, and push the code to your Git repositories.

Notes and limitations

• Some resources may require manual adjustments following import

• Import does not modify live infrastructure during creation