generating-aws-diagrams

AWS DrawIO Diagram Generator

Generates professional DrawIO XML diagrams for Amazon Web Services architectures.

Capabilities

1. Extract - Analyze existing DrawIO XML files to identify AWS shapes, connections, and structure
2. Identify - Recognize AWS service icons from architecture diagram images
3. Generate - Create valid DrawIO XML from images or text descriptions
4. Convert - Transform AWS architecture diagrams into editable DrawIO format

Quick Reference

AWS Shape Patterns

There are two icon types. Use service icons when labeling the AWS service itself, and instance icons when representing a specific resource.

Service icon (colored square background) — for labeling the service:

shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.{shape_name}

Instance icon (bare icon, no background) — for specific resources:

shape=mxgraph.aws4.{shape_name};fillColor={category_color}

CRITICAL: Always keep fillColor set to the category color. Without it the icon renders white/invisible. The only difference from a service icon is the absence of the resourceIcon background square — never remove fillColor when using an instance icon.

| Scenario | Icon Type | Label Example | |----------|-----------|---------------| | The AWS service itself | Service (with background) | "AWS Lambda", "Amazon RDS" | | A specific resource/instance | Instance (no background) | "Order Processor", "Users Table" | | Multiple instances of same service | Instance (no background) | "ECS Task 1", "ECS Task 2" |

CRITICAL: Underscore-Separated Names

Multi-word AWS shape names use UNDERSCORES in style properties!

• step_functions (correct)
• api_gateway (correct)
• kinesis_data_streams (correct)
• step functions (WRONG - will not render)
• api gateway (WRONG - will not render)

The aws4.xml stencil defines names with spaces, but DrawIO's style parser requires underscores.

Always look up exact names in assets/aws-icons.json before using.

Common AWS Services

| Service | Service Icon (with background) | Instance Icon (no background) | |---------|-------------------------------|-------------------------------| | Lambda | shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.lambda | shape=mxgraph.aws4.lambda | | Amazon S3 | shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.s3 | shape=mxgraph.aws4.s3 | | Amazon EC2 | shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.ec2 | shape=mxgraph.aws4.ec2 | | DynamoDB | shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.dynamodb | shape=mxgraph.aws4.dynamodb | | API Gateway | shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.api_gateway | shape=mxgraph.aws4.api_gateway | | Amazon SQS | shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.sqs | shape=mxgraph.aws4.sqs | | Amazon SNS | shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.sns | shape=mxgraph.aws4.sns | | Step Functions | shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.step_functions | shape=mxgraph.aws4.step_functions | | Amazon ECS | shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.ecs | shape=mxgraph.aws4.ecs | | Amazon RDS | shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.rds | shape=mxgraph.aws4.rds |

AWS Container Types

| Container | Use Case | |-----------|----------| | aws_cloud | Top-level AWS Cloud boundary | | aws_region | Region grouping | | aws_availability_zone | AZ grouping | | aws_vpc | VPC boundary | | aws_public_subnet | Public subnet | | aws_private_subnet | Private subnet | | aws_security_group | Security group boundary | | aws_auto_scaling_group | Auto scaling group | | aws_account | AWS Account boundary | | aws_corporate_datacenter | Corporate datacenter | | aws_generic_group | Generic grouping | | aws_step_functions_workflow | Step Functions workflow | | aws_elastic_beanstalk_container | Elastic Beanstalk app |

Task 1: Analyze a DrawIO File

Use this workflow to extract and document all components from an existing DrawIO file.

Steps

1. Read the file - Load the .drawio XML file
2. Parse structure - Extract all <mxCell> elements
3. Identify shapes - Find cells with vertex="1"
4. Identify connections - Find cells with edge="1"
5. Extract styles - Parse style strings for each element
6. Map hierarchy - Build container/child relationships using parent attribute
7. Generate report - Output findings in structured format

Input

• Path to .drawio file

Output

Generate a Markdown report with:

# DrawIO Analysis Report

## Summary
- Total shapes: X
- Total connections: Y
- Containers: Z

## Shape Inventory

| ID | Label | Type | Position | Parent |
|----|-------|------|----------|--------|
| abc | Lambda | mxgraph.aws4.lambda | (100,200) | vpc1 |

## Connection Matrix

| From | To | Label | Type |
|------|-----|-------|------|
| Lambda | DynamoDB | API | solid |

## Container Hierarchy

- VPC (vpc1)
  - Lambda (lambda1)
  - Lambda (lambda2)
  - DynamoDB (db1)

## Style Analysis

### Unique Shapes Found
- mxgraph.aws4.lambda (4 instances)
- mxgraph.aws4.dynamodb (2 instances)

Task 2: Convert Image to DrawIO

Use this workflow to recreate an AWS architecture diagram from an image.

Steps

1. Analyze image - Identify all visual elements:
2. AWS service icons (shape, color, label)
3. Containers/boundaries (color, border style)
4. Connections (solid, dashed, arrows)
5. Labels and text

1. Map to library - For each identified element:
2. Look up in assets/aws-icons.json by visual signature or label
3. Match containers to assets/aws-containers.json
4. CRITICAL: Verify underscore-separated names for multi-word services (e.g., step_functions, not step functions)
5. Note any unrecognized elements

1. Estimate layout - Determine positions:
2. Identify container boundaries first
3. Place icons within containers
4. Estimate x,y coordinates and dimensions
5. Standard icon size: 64x64 pixels

1. Generate XML - Build the DrawIO structure:
2. Start with base template from assets/templates/drawio-base.xml
3. Add containers first (they become parents)
4. Add service icons with correct parent references
5. Add connections between shapes

1. Create confidence report - Document accuracy:
2. List all identified components
3. Note any uncertain matches
4. Flag potential issues

Input

• AWS architecture diagram image (PNG/JPG)

Output

1. Valid .drawio XML file
2. Confidence report (Markdown)

Confidence Report Format

# Conversion Confidence Report

## Overall Confidence: 85%

## Identified Components

### High Confidence (>90%)
- Lambda x4 - Clear icon match
- DynamoDB x2 - Clear icon match
- VPC container - Purple border, correct label

### Medium Confidence (70-90%)
- Step Functions - Icon similar, label confirms (using `step_functions` with underscores)

### Low Confidence (<70%)
- Unknown icon at position (300, 400) - Mapped to generic service

## Connection Accuracy
- 12/14 connections clearly visible
- 2 connections inferred from layout

## Notes
- VPC subnet grouping identified
- Bidirectional arrows on 3 connections

Task 3: Create DrawIO from Description

Use this workflow to generate a new AWS diagram from text specifications.

Steps

1. Parse requirements - Extract from description:
2. Required AWS services
3. Container/grouping needs
4. Connection requirements
5. Layout preferences

1. Select components - From libraries:
2. Look up services in assets/aws-icons.json
3. Choose containers from assets/aws-containers.json
4. Choose icon type: Use service icons (with background) for generic service labels, instance icons (no background) for specific resources (see Quick Reference)
5. VERIFY: Underscore-separated names for multi-word services in style strings
6. Sel