Use Lucid AI’s Cloud Agent to build architecture diagrams in Lucidchart

Written by:  Morgan T
Last updated:  

With Cloud Agent (beta) functionality, you can use Lucid AI to generate targeted cloud infrastructure diagrams directly inside Lucidchart. By inspecting your imported cloud data, the Cloud Agent builds tailored visuals customized to a specific audience, question, or stakeholder, allowing you to bypass overwhelming default layouts and see only the data relevant to your needs.

Cloud Agent is available for accounts with the Cloud Accelerator. Contact sales to purchase the Cloud Accelerator for your Enterprise account. 

Cloud Agent is currently in beta and is available to all licensed Cloud Accelerator accounts. It is only available for AWS at this time.

Create a diagram with the Cloud Agent

To generate a narrative cloud diagram using the agent, follow these steps:

  1. Open a new or existing Lucidchart document through the Data Hub.
  2. Select lucid-ai-icon.png the Lucid AI icon from the top of the Primary Toolbar on the left side of the page.
  3. Click the plus sign icon in the bottom-left corner of the text box.
  4. Select Cloud Agent.
  5. Input a prompt or diagram request in the chat panel.
  6. Answer any clarifying follow-up questions from the agent to help scope your diagram, such as specifying accounts, regions, or specific application tags.

The agent queries the appropriate subset of your data and generates data-backed shapes on the canvas where coverage allows.

Example prompts in Lucid AI’s Cloud Agent

When getting started or testing the capabilities of the Cloud Agent, use specific criteria in your prompts to yield the best results. As the beta experience iterates, prompts will require less explicit detail, but utilizing these starting points ensures a strong baseline:

Audit diagrams

  • Prompt: "Create a network segmentation diagram for my upcoming SOC 2 audit."
  • Best practices for specificity: Share any tags you use to indicate what is in scope, or ask the agent to focus on a specific account or region.

Serverless flows

  • Prompt: "Show me the serverless flows I have in place, grouped by application."
  • Best practices for specificity: If you use a specific tag name (such as applicationName) to organize your resources, specify that name, and clarify which applications you are primarily interested in.

Network topology

  • Prompt: "Give me an overview of my network topology."
  • Best practices for specificity: This prompt works well for showing cross-account relationships in multi-account environments. Specify if you have a shared network hub account. You should also indicate how to distinguish which accounts or regions are in scope (for example, by calling out tags used for production versus staging environments).

Regional or application overviews

  • Prompt: "Create a diagram showing the resources running in my primary region, organized by application" (or "by networking structure").
  • Best practices for specificity: View more detailed sections of your environment by explicitly stating the resource types you want to see or what specific containers you want visualized (such as subnets versus security groups).

FAQ

Why are some resources missing or incorrect in the generated diagram?
The Cloud Agent relies on your imported Data Hub metadata, tagging conventions, and prompt clarity to identify resources. If your data is missing or your prompt is ambiguous, the agent may hallucinate nonexistent resources or omit expected ones. To fix this, verify your imported data types in the Data Hub and re-prompt the agent with explicit names, tags, or region references.

How can I improve a cluttered and hard-to-read cloud diagram?
By default, the Cloud Agent maps out each individual connection to give you complete visibility. For large environments, this high level of detail can get crowded. To streamline your view, try prompting the agent to collapse specific containers, or narrow your scope to focus on a single region, application, or account at a time.

Can I rearrange the layout instead of stacking resources in a single column?
Yes. To keep your initial import organized, the beta auto-layout defaults to a clean vertical stack. This gives you a clear baseline to work from. Because every architecture is unique, you have full flexibility to drag, drop, and rearrange the shapes on the canvas to design the layout that works best for your team.

Resources

To learn more about this feature, explore the additional resources below. These resources are available in English only.

Community post 
Best practices, workarounds, and feedback while working with the Cloud Agent

Give feedback on this article

Have feedback about this article? Tell us about your experience here.

Did you find what you were looking for?

Still have a question or want to share what you have learned? Visit our Community   to get help and collaborate with others.