Cloud Resource Import
Cloud Resource Import connects the live inventory view to the agent workflow. You start fromCloud Resources, select one or more discovered resources, choose a repository, and
let Cloudgeni create an agent-backed import session.
What You Need First
- An active cloud integration
- A repository available through a Git integration
Single-Resource Import
For a single resource, the product gives you the most control. The resource detail flow lets you:- Open the resource directly
- Browse the target repository tree
- Choose the file or folder path that should receive the generated IaC
- Start the import with that path already attached to the request
Multi-Resource Import
For multiple resources, the flow is simpler by design.- Select resources from the Cloud Resources list
- Use the selection dock to move into the bulk import page
- Choose the target repository
- Add optional instructions
- Start the import session
What Happens Under The Hood
The import request is sent through the cloud resources remediation API and then handed off into the same agent-session system used elsewhere in the product. That means the output is still repository-first:- Proposed files or edits
- Branch and PR flow when appropriate
- A session you can continue instead of a one-shot import result
Good Uses
- Rebuilding missing IaC for existing resources
- Capturing a small group of related resources into a repository
- Starting from discovered cloud state instead of starting from a blank repo
Bad Uses
- Large-scale estate migration in one pass
- Cases where you do not yet know which repository should own the resource
- Workflows where you expect Cloudgeni to apply the change directly in cloud
Next
AI DevOps
Continue the generated import in an agent session.
Connect Cloud
Set up the cloud account side if you have not done that yet.