modelscope.cn

aws-architecture-diagram

AWS architecture diagrams — generate visual network topology diagrams from live AWS infrastructure. Use when drawing AWS network diagrams, visualizing VPCs, mapping Transit Gateway topology, or generating architecture documentation.

Installation

$ npx skills add https://modelscope.cn

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from modelscope.cn · top by installs.

npx skills add https://modelscope.cn

Browse all from modelscope.cn

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
LicenseApache-2.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,814 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

AWS Architecture Diagram

MCP Server

  • Command: uvx awslabs.aws-diagram-mcp-server@latest (stdio transport)
  • Requires: AWSACCESSKEYID, AWSSECRETACCESSKEY, AWSREGION (or AWSPROFILE)
  • Dependency: Requires graphviz installed on the system (apt install graphviz or brew install graphviz)

Key Capabilities

  • Auto-discovery: Scan AWS account and render infrastructure as a diagram
  • Network topology: VPCs, subnets, route tables, IGW, NAT GW, TGW connections
  • Service mapping: EC2, ELB, RDS, Lambda placed in their VPC/subnet context
  • Multiple formats: PNG, SVG, PDF output
  • Filtered views: Scope diagram to specific VPCs, services, or tags

Workflow: Network Architecture Diagram

When a user asks "draw our AWS network" or "show me the architecture":

  1. Generate diagram: Use diagram tool scoped to networking resources
  2. Include: VPCs, subnets (public/private), IGW, NAT GW, TGW, VPN, peering connections
  3. Label: CIDR blocks, subnet names, AZ placement
  4. Connections: Show routing paths — TGW attachments, peering links, VPN tunnels
  5. Output: PNG or SVG file for sharing in Slack or documentation
  6. Report: Architecture summary alongside the diagram

Workflow: VPC Detail Diagram

When focusing on a specific VPC:

  1. Scope to VPC: Filter diagram to one VPC by ID or tag
  2. Show subnets: Public, private, isolated — grouped by AZ
  3. Show route tables: Main and custom route tables with key routes
  4. Show gateways: IGW, NAT GW, VPC endpoints
  5. Show security: NACLs, security group relationships
  6. Output: Detailed VPC topology diagram

Workflow: Multi-Account Network Diagram

When documenting cross-account architecture:

  1. Hub-spoke topology: Show Transit Gateway as the hub
  2. VPC attachments: Each spoke VPC with its CIDR and purpose
  3. Route propagation: Show which routes propagate where
  4. VPN/DX: On-premises connections via VPN or Direct Connect
  5. Inspection VPC: Network Firewall placement if applicable
  6. Output: Enterprise network topology diagram

Integration with Other Skills

Skill How They Work Together
aws-network-ops Discover VPCs/TGWs first, then diagram them
aws-cloud-monitoring Add CloudWatch metrics annotations to diagram
aws-cost-ops Annotate diagram with cost per resource
markmap-viz Generate mindmap alternative for simpler overviews

Diagram Scoping Tips

Scope When To Use
Full account Initial architecture review or documentation
Single VPC Troubleshooting or VPC-specific audit
TGW + attachments Multi-VPC connectivity review
Subnet-level Security audit or routing investigation
Tagged resources Application-specific or team-specific views

Important Rules

  • Graphviz required — the MCP server generates Graphviz DOT files and renders them; graphviz must be installed
  • Large accounts may produce complex diagrams — scope with filters for clarity
  • Region-specific — diagram shows resources in the configured AWS_REGION only
  • Read-only — only discovers and renders, never modifies resources
  • Record in GAIT — log diagram generation for audit trail

Environment Variables

  • AWSACCESSKEYID, AWSSECRETACCESSKEY, AWSREGION (or AWSPROFILE)