Transform Terraform, CloudFormation, and other Infrastructure-as-Code into beautiful, professional architecture diagrams. Automatically. In your CI/CD pipeline.
# template.yaml (CloudFormation)
AWSTemplateFormatVersion: '2010-09-09'
Description: Secure serverless website (AWS) - S3 private origin + CloudFront + WAF
Resources:
LogsBucket:
Type: AWS::S3::Bucket
Properties:
BucketEncryption:
ServerSideEncryptionConfiguration:
- ServerSideEncryptionByDefault:
SSEAlgorithm: AES256
SiteBucket:
Type: AWS::S3::Bucket
Properties:
BucketEncryption:
ServerSideEncryptionConfiguration:
- ServerSideEncryptionByDefault:
SSEAlgorithm: AES256
VersioningConfiguration:
Status: Enabled
LoggingConfiguration:
DestinationBucketName: !Ref LogsBucket
LogFilePrefix: s3/
SiteBucketPublicAccessBlock:
Type: AWS::S3::BucketPublicAccessBlock
Properties:
Bucket: !Ref SiteBucket
BlockPublicAcls: true
IgnorePublicAcls: true
BlockPublicPolicy: true
RestrictPublicBuckets: true
WafAcl:
Type: AWS::WAFv2::WebACL
Properties:
Name: auto-arch-waf
Scope: CLOUDFRONT
DefaultAction: ...
↑ Auto-generated from your CloudFormation code
Keep your documentation in sync with your infrastructure, automatically.
Diagrams regenerate on every PR, ensuring documentation never drifts from reality.
Native support for AWS, Azure, and GCP with official cloud icons and styling.
Export to PNG, SVG, JPEG, Mermaid, and Markdown. Use anywhere.
Uses official AWS, Azure, and GCP architecture icons for polished diagrams.
Works out of the box. Just add to your workflow and push.
Automatically detects resource relationships and dependencies from your code.
Add to your GitHub Actions workflow in seconds.
name: Update Architecture Diagram on: pull_request: paths: - '**/*.tf' - '**/*.yaml' jobs: diagram: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Generate Architecture Diagram uses: suryakumaran2611/auto-arch-diagram@v1 with: iac_globs: **/*.tf\n**/*.yaml out_dir: artifacts image_formats: png,svg mode: static direction: LR - name: Upload Diagram Artifacts uses: actions/upload-artifact@v4 with: name: architecture-diagram path: artifacts/
Best Practice: Use iac_globs to specify all relevant IaC files (Terraform, CloudFormation, etc.) and out_dir for organized output. Always upload generated artifacts for traceability.
Automatically publish or robustly replace architecture diagrams in your Confluence pages using the Auto Arch Diagram GitHub Action.
jobs: diagram: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: suryakumaran2611/auto-arch-diagram@v1 with: publish_to_confluence: true confluence_url: https://your-domain.atlassian.net/wiki confluence_page_id: 123456 confluence_username: ${{ secrets.CONFLUENCE_USER }} confluence_api_token: ${{ secrets.CONFLUENCE_API_TOKEN }} confluence_marker: ARCH_DIAGRAM_MARKER
Best Practice: Use a unique marker (e.g., ARCH_DIAGRAM_MARKER) in your Confluence page to target the diagram for replacement. The action will only update the image between these markers, ensuring robust and precise updates.
How to Add a Marker: In your Confluence page, add a comment or text like <!-- ARCH_DIAGRAM_MARKER --> before and after the diagram image. The action will replace the image between these markers.
Troubleshooting:
Export your diagrams in the format that works best for you.
High-quality raster images with transparent or white background
Scalable vector graphics, perfect for documentation
Renders natively in GitHub, Notion, Confluence & more
Ready to embed in your README or wiki
Real-world architecture diagrams generated automatically from Terraform code.
Enterprise machine learning architecture spanning AWS, Azure, and GCP for model training, serving, and data analytics.
Primary and disaster-recovery regions in one AWS cloud boundary with VPC peering and cross-region data flow.
Complex serverless ETL workflow using custom icons for conceptual services like triggers, processors, and streams.
Large-scale AWS MLOps stack with training, orchestration, feature store, and cross-region recovery topology.
Dual-VPC architecture with public/private subnet tiers, route tables, and explicit peering connectivity.
Event-driven ingestion, cataloging, transformation, and storage layers with strong IAM and observability paths.
EKS-centric microservices architecture with network isolation, persistent data services, and secure IAM edges.
Classic web, app, and data-tier design with load balancing, subnet segmentation, and service dependencies.
Asynchronous event architecture with API Gateway, Lambda, SNS/SQS, and DynamoDB workflows.
AWS and GCP hybrid architecture combining cross-cloud data movement and mixed compute/data services.
Minimal example showing essential network and compute relationships for quick onboarding and validation.
CloudFormation-powered secure static website with S3, CloudFront, and WAF protection.