Generate Draw.io XML architecture diagrams with accurate AWS service icons. Use when the user asks to create, update, or visualize an AWS architecture diagram, or mentions Draw.io diagrams for AWS infrastructure.
Generate Draw.io XML architecture diagrams with accurate AWS service icons.
When the user asks to create, update, or generate an AWS architecture diagram in Draw.io format.
Read the relevant reference files to get exact shape names and colors:
references/aws-icons-compute.md — EC2, Lambda, ECS, EKS, Fargate, ELBreferences/aws-icons-storage-database.md — S3, EBS, RDS, DynamoDB, Aurora, ElastiCachereferences/aws-icons-networking.md — VPC, CloudFront, Route 53, API Gateway, Direct Connectreferences/aws-icons-app-integration.md — SNS, SQS, EventBridge, Step Functions, CloudWatch, CloudFormationreferences/aws-icons-analytics-ml.md — Athena, Glue, Kinesis, OpenSearch, Bedrock, SageMakerreferences/aws-icons-security.md — IAM, Cognito, WAF, Shield, KMS, GuardDutyreferences/aws-icons-common.md — Users, servers, internet, groups, arrowsCRITICAL: Always look up icons before generating XML. Never guess icon names.
Read references/layout-guidelines.md for spacing, nesting, and style rules.
Key layout decisions:
Use templates/base.drawio.xml as the skeleton. Build XML with these patterns:
<mxCell id="svc-lambda" value="Lambda" style="sketch=0;points=[[0,0,0],[0.25,0,0],[0.5,0,0],[0.75,0,0],[1,0,0],[0,1,0],[0.25,1,0],[0.5,1,0],[0.75,1,0],[1,1,0],[0,0.25,0],[0,0.5,0],[0,0.75,0],[1,0.25,0],[1,0.5,0],[1,0.75,0]];outlineConnect=0;fontColor=#232F3E;fillColor=#ED7100;strokeColor=#ffffff;dashed=0;verticalLabelPosition=bottom;verticalAlign=top;align=center;html=1;fontSize=12;fontStyle=0;aspect=fixed;shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.lambda;" vertex="1" parent="grp-subnet">
<mxGeometry x="100" y="50" width="48" height="48" as="geometry" />
</mxCell>
MANDATORY: strokeColor=#ffffff for resourceIcon pattern. This makes the glyph white.
<mxCell id="res-lambda-fn" value="Lambda Function" style="sketch=0;outlineConnect=0;fontColor=#232F3E;gradientColor=none;fillColor=#ED7100;strokeColor=none;dashed=0;verticalLabelPosition=bottom;verticalAlign=top;align=center;html=1;fontSize=12;fontStyle=0;aspect=fixed;pointerEvents=1;shape=mxgraph.aws4.lambda_function;" vertex="1" parent="grp-subnet">
<mxGeometry x="100" y="50" width="48" height="48" as="geometry" />
</mxCell>
<mxCell id="grp-vpc" value="VPC" style="sketch=0;outlineConnect=0;fontColor=#232F3E;fontStyle=0;container=1;collapsible=0;recursiveResize=0;shape=mxgraph.aws4.group;grIcon=mxgraph.aws4.group_vpc2;strokeColor=#8C4FFF;fillColor=none;verticalAlign=top;align=left;spacingLeft=30;fontColor=#AAB7B8;dashed=0;" vertex="1" parent="grp-region">
<mxGeometry x="30" y="40" width="800" height="400" as="geometry" />
</mxCell>
<mxCell id="edge-1" value="HTTPS" style="edgeStyle=orthogonalEdgeStyle;html=1;endArrow=block;elbow=vertical;startArrow=none;endFill=1;strokeColor=#545B64;rounded=0;fontSize=10;fontColor=#545B64;" edge="1" source="svc-cloudfront" target="svc-apigw" parent="1">
<mxGeometry relative="1" as="geometry" />
</mxCell>
Choose a descriptive kebab-case slug that best describes the diagram content (e.g., realtime-data-pipeline, event-driven-orders, multi-tier-web-app). Use this slug for both output files.
docs/<slug>.drawio (e.g., docs/realtime-data-pipeline.drawio)docs/<slug>.md.drawio in Draw.io to verifystrokeColor=#ffffff for all resourceIcon patterns (service-level icons)strokeColor=none for all dedicated shapes (resource-level icons)#545B64 (AWS default gray)#F5F5F5 rounded rect behind everything (title, lanes, legend) so PNG export has a clean background instead of blackWhen the diagram targets non-technical viewers (managers, stakeholders, end users):
Replace technical labels (HTTPS, REST API, etc.) with circled step numbers:
When a diagram has multiple flows (e.g., data processing + search), use swim lanes:
"① チケット取得 → ② データ保存 → ③ AI変換 → ④ 索引化"#F5F5F5 rounded rect behind everything (title + lanes + legend)fontColor=#232F3E (not gray) for readability on any export backgroundWhen a diagram includes AWS managed services (S3, Bedrock, OpenSearch, etc.) accessed from within a VPC:
rounded=1;whiteSpace=wrap;fillColor=none;strokeColor=#879196;strokeWidth=1;dashed=1;dashPattern=4 4;fontColor=#232F3E;fontSize=12;fontStyle=1;verticalAlign=top;align=left;spacingLeft=10;spacingTop=8;container=1;collapsible=0;
| Category | fillColor |
|---|---|
| Compute & Containers | #ED7100 |
| Storage | #7AA116 |
| Database | #C925D1 |
| Networking & CDN | #8C4FFF |
| Analytics | #8C4FFF |
| App Integration & Mgmt | #E7157B |
| AI / Machine Learning | #01A88D |
| Security | #DD344C |
| General | #232F3E |