Skip to content
Connect an agent
Cloud architecture

Icon names and lookup

How a cloud product becomes an icon= name, how search finds it, and how to map the product names in a request to icons with the tools. It is for an AI agent first; a person can use the icon pages in the same way.

TL;DR

QuestionAnswer
What is the shape of a name?<provider>:<product>, in lowercase words joined with hyphens, without the provider's name repeated: aws:lambda, azure:cosmos-db, gcp:cloud-run.
How do I get the icon for a group?The provider itself is <provider>:cloud. Set type= and provider= on the group and it draws the right one.
How do I find the name of one product?Call search_icons with the product name as the request writes it, and use the first result.
How do I find the names of many products?Call map_icons once with up to 40 names and the provider. Each name comes back resolved, with a confidence, or with the candidates to choose from.
What if nothing matches?The name is listed in gaps with a neutral fallback. Draw the service with its node type and put the product name in the label.
Where can I see the icons?On the icon pages: AWS, Azure, Google Cloud, other providers, and generic and technology icons.
Can I guess a name?No. An unknown name is an error with the nearest valid names, so validation catches a guess, but a search is faster than a retry. A few everyday words are aliases that draw anyway: lucide:cart draws lucide:shopping-cart and comes back as note I122 with the real name.

1. How a name resolves

An icon reference is a set, a colon, and a name. The set says where the artwork comes from, and the name says which one. The provider sets hold the products of one cloud each.

SetHoldsExample
aws, azure, gcpThe provider's products, one page of icons eachaws:s3, azure:key-vault, gcp:bigquery
alibaba, oci, ibm, cloudflare, digitalocean, vercelOther providers, with fewer products, on one pagealibaba:oss, cloudflare:workers
simpleTechnology and brand logossimple:postgresql, simple:auth0, simple:angular
lucideGeneral iconslucide:git-branch
statusColored outcome iconsstatus:success

The names come from the product's own name, so they are stable.

A general icon is often guessed by an everyday word instead of its Lucide name. A hundred such words are aliases of a bundled icon: the diagram draws the icon, and validation returns note I122 in notices, which is information and never an error. Write the real name to clear it. A name that is neither bundled nor an alias is still error E122.

WrittenDraws
lucide:cart, lucide:basket, lucide:checkoutlucide:shopping-cart
lucide:banklucide:landmark
lucide:support, lucide:helpdesk, lucide:customer-supportlucide:headset
lucide:edit, lucide:penlucide:pencil
lucide:delete, lucide:trash-2lucide:trash
lucide:homelucide:house
lucide:money, lucide:cashlucide:banknote

search_icons and map_icons find each icon by the same words, so a search for cart or bank returns the icon first.

2. How search finds a product

search_icons understands how people name products. Relevance, best first:

RankA query that isExample
1Exactly a product's name, title, or alias, with or without its providerlambda, aws lambda, s3 bucket, azure functions
2A provider followed by a kind of serviceazure object storage
3Two or more words inside a title or aliasblob storage
4A phrase for a kind of servicemessage queue finds every provider's queue
5Words that match a name, a concept phrase, or a tagtoken exchange, defect

A phrase for a kind of service wins over a product that happens to be named that, so load balancer lists every provider's load balancer, most used provider first. Some examples of what comes back:

You searchYou getWhy
lambda, aws lambda, AWS Lambdaaws:lambdaA product name, with or without the provider
cosmos, cosmos db, cosmosdbazure:cosmos-dbAn alias or abbreviation
gke, google kubernetes enginegcp:gkeAn abbreviation and the full title
serverless functionThe function product of each provider, most used provider firstA kind of service
azure message queueazure:service-busA provider followed by a kind of service

3. Map the product names of a request

A request such as "a web app with a Postgres database, a queue for slow work, and a CDN, on AWS" names several products. Map them all at once.

  1. List the names. Take each service as the request writes it: Postgres, queue, CDN, web app. Do not translate them first.
  2. Call map_icons. Send the names and set provider to the cloud the architecture runs on, so that a generic name such as queue finds that cloud's product (aws:sqs) first.
  3. Read the confidence of each result. Write the icon of a result whose resolved is true. For ambiguous, choose from candidates, or ask the user, because a kind of service several clouds offer, or a match by idea only, is not a decision for the tool.
  4. Handle the gaps. A name in gaps matched nothing. Use the fallback, or leave icon= off so the node type draws its own, and put the name in the label.
  5. Validate. Call validate_diagram or draw_diagram. A node whose label names a product but has no icon gets warning W204 with the exact text to add.
ConfidenceMeaningWhat to do
exactThe name is the icon or the product nameUse icon
strongThe name clearly points at this icon and no other provider competesUse icon
ambiguousSeveral icons fit, or the match is by idea onlyChoose from candidates, or ask

For one name, search_icons returns the matches best first, and the first is the answer. map_icons replaces up to 40 of those calls.

4. Read an icon page

Each icon page lists every icon of a set, grouped by the provider's own categories, with the same layout throughout.

PartWhat it shows
Category headingThe provider's category, such as Compute or Databases
PictureThe icons of the category as the renderer draws them, each above its product name
TableThe exact icon= for each product, its official name, and other names that find it. On the AWS, Azure, and Google Cloud pages it is folded under the picture.

The pictures are extra: a table row holds everything an agent needs, and the picture lets a person see the icon before using it.

5. What an icon draws

Every cloud product draws one of three things, and the name, the search, and the validation are the same whichever it is, so a diagram means the same thing everywhere.

ArtworkWhere it comes from
The vendor's own iconThe official architecture icon of AWS, Azure, or Google Cloud, drawn as the vendor published it, in its original colors, on a light tile in both themes, next to the product name
A brand markA licensed mark, such as the mark of Cloudflare, drawn in the color of the node or group that holds it
The glyph of a kind of serviceA function, a queue, or object storage looks the same on every cloud, and the label says whose it is

See Trademarks and icons for the terms the artwork is used under.

See also

DocWhy
Cloud architectureThe five-step recipe
AWS iconsEvery AWS icon, drawn
Azure iconsEvery Azure icon, drawn
Google Cloud iconsEvery Google Cloud icon, drawn
Trademarks and iconsThe terms for the vendor artwork and the marks
Icon referenceThe compact catalog of every bundled icon
Tool referencemap_icons, search_icons, and draw_diagram