# Cloud architecture

> Create cloud/software system architecture diagrams — backend, microservices, deployment, infrastructure, integration or network architecture — for AWS, Azure, GCP, Kubernetes, SAP, or generic syste…

Source: https://mockflow.com/developers/reference/item-types/cloud-architecture

Send `"type": "cloud_architecture"`.

Create cloud/software system architecture diagrams — backend, microservices, deployment, infrastructure, integration or network architecture — for AWS, Azure, GCP, Kubernetes, SAP, or generic systems (use "aws" icons when no provider is named). ONLY for technical software/cloud/network diagrams — NOT for physical buildings, construction, or real-world/building architecture.

Also available as the MCP tool `render_cloudarchitecture`. The same payload works through either surface.

### Fields

- `title` (string): A short title for the diagram, shown as the frame header (e.g. "AWS Web App Architecture").
- `diagramType` (enum<string>, required): Cloud provider / platform — picks the icon set the client renders with. Default "aws" when the request names no provider. One of `aws`, `azure`, `gcloud`, `kubernetes`, `sap`, `sapbtp`, `oracle` or `cisco`.
- `flowDirection` (enum<string>): The axis the architecture reads along, and the axis the layout engine lays the sections along. "vertical" for sections that are stages of one thing (tiers, layers, planes, phases, a stack, an ingest/process/store pipeline); "horizontal" for sections a request travels between (an outside actor, a network, a region, a provider boundary). Prefer "vertical" when both fit. One of `horizontal` or `vertical`.
- `class` (string): GoJS model class, typically 'GraphLinksModel'
- `nodeDataArray` (object[], required): Cloud components and groups. Each node: key (string), text, type, color, fillColor, fontColor, loc ("x y" rough reading order), isGroup (true for containers), group (parent group key). "color" is REQUIRED on every group/section and is what the section is painted from, so give each one a tone its neighbours do not have; fontColor is optional and follows color. No width/height — the renderer sizes everything.
- `linkDataArray` (object[]): Connections: from, to (node keys), text (optional label, at most 2 words and 16 characters, and only on about a third of the links). One link per pair, no link between a node and a section that contains it. No fromSpot/toSpot — the renderer picks sides from the final layout.

## Example

```json
{
  "type": "cloud_architecture",
  "data": {
    "title": "Q4 Launch Planning",
    "diagramType": "aws",
    "flowDirection": "horizontal",
    "class": "string",
    "nodeDataArray": [
      {}
    ],
    "linkDataArray": [
      {}
    ]
  }
}
```