aws-drawio-architecture-diagrams_skill

Overview

This skill generates production-ready AWS architecture diagrams in draw.io XML (.drawio) format using the official AWS Architecture Icons (aws4). It produces fully-formed .drawio files with correct groups, service icons, connector styles, and layout rules so files open directly in diagrams.net with aws4 libraries enabled. Use it to create repeatable, precise visual documentation of AWS infrastructure.

How this skill works

The skill builds draw.io XML that follows the required mxfile/mxGraphModel root structure, reserved root cells, sequential numeric IDs, and landscape page dimensions. It inserts nested aws4 group containers (AWS Cloud, Region, VPC, Subnets) and resourceIcon or dedicated shapes with the correct style attributes (including strokeColor=#ffffff for resourceIcon shapes). Connectors use predefined styles for standard, secure, and async flows and all coordinates, sizes, and spacing align to the grid and layout best practices.

When to use it

• Designing VPCs, subnets, and network topology diagrams
• Documenting serverless or multi-tier application architectures
• Creating deployment diagrams for ECS, EKS, EC2, ALB, and RDS
• Visualizing data pipelines, analytics, or cross-region DR setups
• Producing diagrams for Well-Architected reviews or architecture proposals

Best practices

• Keep hierarchy: External → Internet → AWS Cloud → Region → VPC → Subnets → Services
• Use landscape pageWidth=1169 and pageHeight=827 and grid-aligned coordinates (multiples of 10)
• Use standard icon sizes (60x60) and 30–40px spacing between icons
• Set strokeColor=#ffffff on all mxgraph.aws4.resourceIcon shapes so glyphs render white
• Place labels below icons and follow left-to-right traffic flow for clarity
• Nest resources in container groups with container=1 and reference parent IDs correctly

Example use cases

• Generate a three-tier web app diagram with public ALB, private EC2 app servers, and RDS in data subnets across AZs
• Create a serverless architecture diagram with API Gateway → Lambda → DynamoDB and S3
• Produce a VPC layout showing public/private subnets, NAT/IGW, and security group boundaries
• Build a data pipeline diagram with Kinesis → Glue → Redshift and S3 storage