Cloud Architecture
Create cloud architecture diagrams for AWS, Azure, GCP, and more. Design scalable infrastructure with professional cloud icons.
Yes—and you probably should. Learn how to build and manage custom icon libraries in draw.io, Lucidchart, Miro, and when AI-powered tools make more sense.
Click Cloud Architecture to open AI Line Studio and generate diagrams from natural language in seconds.
When you draw an architecture diagram using a generic "server" icon instead of a proper EC2 instance or an Azure VM, you lose specificity. Your diagram communicates less than it could. For architecture and system diagrams, specificity is the difference between a diagram that clarifies and one that merely decorates.
Here's how to build them, manage them, and avoid the common traps.
Consistency. When everyone on your team uses the same icon set, diagrams look like they belong together. No more mixing flat icons with 3D icons, or using different AWS icon generations in the same diagram.
Speed. Once a custom library exists, you drag and drop. No hunting through shape menus, no resizing mismatched icons, no reformatting.
Accuracy. Official cloud provider icons change. AWS, Azure, and GCP update their icon sets regularly. A custom library built from the latest official assets ensures your diagrams reflect current visual standards.
Branding. Your company has a visual identity. Your diagrams should too.
draw.io gives you several ways to work with custom icons, ranging from personal shortcuts to team-wide libraries.
The Scratchpad is your personal shape stash. Add frequently used icons, groups of shapes, or entire diagrams. To add shapes: select a shape (or multiple with Ctrl/Cmd+click), then click the + icon on the Scratchpad. If you don't see it, go to View → Scratchpad.
This is the quickest path for individual use, but it's not shareable and doesn't persist across devices.
For teams, create a proper custom library file (.xml). Go to File → New Library and choose where to save it. Drag shapes from your canvas onto the library, or select a shape and click the + icon next to the library name. Once saved, share the .xml file with your team.
If you're using draw.io for Confluence Cloud, admins can upload custom libraries via Settings → Configuration → Custom Libraries. Upload the .xml file, and it becomes available to everyone under +More Shapes. You can also configure the editor with JSON to set default fonts, color palettes, and corporate logos globally.
Host your library on GitHub or any public URL. Use File → Open Library from → URL to load it directly. This is useful for sharing libraries without distributing files. For example, you can load community libraries like the Azure icon set maintained by the diagrams.net community.
Pro tip: You can also drag and drop images directly onto the canvas or import from device via File → Import from → Device. For XML-based custom shapes, use Arrange → Insert → Shape to edit the geometry directly.
Lucidchart supports custom shape libraries with a straightforward workflow.
Create a library: Click More shapes at the bottom of the Shape menu, expand the "My libraries" tab, and click the + icon. Name your library.
Add shapes: Drag a shape from the canvas into an existing custom library. Alternatively, right-click a shape, select Add to Custom Shape Library, and choose your library.
Import from device: You can upload SVG or Visio stencil (.vssx) files directly into a custom library. Click the + sign tile in your library and select Choose file(s).
Lucidchart also supports the Streamline icon integration, giving you access to a massive icon library within the tool.
Miro's custom shape packs are available on Business, Education, and Enterprise plans.
Upload shapes: Access the shapes menu via the Shapes and lines tool, select More shapes, then Browse and upload shapes. Each shape pack can contain up to 100 shapes, max 50KB per file, in SVG format.
Sizing matters: Miro's built-in icons are 80x80px. If your SVG specifies a different size (e.g., 32x32), Miro scales it up, which can produce inconsistent results. Set your desired width and height in the SVG code before uploading. For non-square shapes, specify the intended dimensions and Miro will respect them.
Share with your team: Custom shape packs can be shared with all users in your organization via the dropdown in the My Shapes panel. Admins can manage, edit, or remove shared packs.
Tools like AI Line Studio take a different approach. Instead of managing icon libraries manually, the tool handles icon selection for you.
You describe your system in plain language — "a 3-tier web app on AWS with RDS and a CDN" — and it generates a diagram using 3,000+ officially licensed icons across AWS, Azure, GCP, and OCI. You don't need to build or maintain an icon library; the tool's library is always current with official provider assets.
The tradeoff: you can't add custom proprietary icons (e.g., your company's internal service icons). For teams with bespoke components, AI generation works best as a starting point, with manual adjustments for custom elements.
Official cloud provider assets:
Community-curated collections:
Build your own: For proprietary services or internal components, create SVG icons yourself. Tools like Figma, Illustrator, or even Inkscape work well. Export as SVG and import into your diagramming tool.
1. Centralize ownership. Assign one person or team to maintain the master library. Without a single source of truth, you'll end up with multiple versions, inconsistent updates, and confusion.
2. Version your libraries. Treat your icon library like code. Store the source files (SVGs, XML) in version control. When official icons update, you can track what changed.
3. Standardize on SVG. SVG scales without quality loss, works across all major diagramming tools, and is editable. Avoid PNG or JPG for icons.
4. Follow provider sizing conventions. AWS icons, for example, have specific size ratios. If you mix arbitrary sizes, your diagrams look unprofessional. Stick to the dimensions your tool expects (e.g., Miro's 80x80px default).
5. Document your library. Create a legend or reference page showing each icon and what it represents. This is especially important for proprietary or custom icons that aren't self-explanatory.
6. Review and refresh quarterly. Cloud providers update icons regularly. Set a calendar reminder to check for updates and refresh your library.
7. Don't over-customize. If an official icon exists for a service, use it. Custom icons should fill gaps — proprietary services, internal components, or branding elements — not replace standard ones.
You're a solo practitioner. If you're the only one creating diagrams, the Scratchpad or personal library is sufficient. Building a full team library is overkill.
You rarely create diagrams. If diagramming is a once-a-quarter activity, the effort to build and maintain a custom library isn't justified.
Your stack changes constantly. If you're spinning up and down new services weekly, keeping a custom library current becomes a maintenance burden. AI-powered tools that pull from up-to-date official sources may be a better fit.
You need diagrams for external audiences only. If your diagrams are for client presentations or public documentation, generic icons are often clearer than custom ones. Your audience may not recognize your internal icon set.
Custom icon libraries are one of those things that look like extra work until you've built them — and then you wonder how you ever lived without them. They standardize documentation, speed up diagram creation, and make your architecture diagrams more accurate and professional.
Start small. Build a library for your most-used services. Share it with your team. Iterate. Within a few weeks, you'll have a library that saves everyone time and produces consistently better diagrams.
And if you're starting from scratch and need production-ready diagrams immediately, AI-powered tools like AI Line Studio can generate them with official icons while you build out your custom library in parallel.