base on Diagram-as-code for AWS architecture. # Diagram-as-code This command line interface (CLI) tool enables drawing infrastructure diagrams for Amazon Web Services through YAML code. It facilitates diagram-as-code without relying on image libraries. The CLI tool promotes code reuse, testing, integration, and automating the diagramming process. It allows managing diagrams with Git by writing human-readable YAML. Example templates are [here](examples). Check out the [Introduction Guide](doc/introduction.md) as well for additional information. <img src="doc/static/introduction2.png" width="800">  ## Getting started ### for Gopher (go 1.21 or higher) ``` $ go install github.com/awslabs/diagram-as-code/cmd/awsdac@latest ``` ### for macOS user ``` $ brew install awsdac ``` ## Usage ``` awsdac <input filename> [flags] Flags: -c, --cfn-template [beta] Create diagram from CloudFormation template -d, --dac-file [beta] Generate YAML file in dac (diagram-as-code) format from CloudFormation template -h, --help help for awsdac -o, --output string Output file name (default "output.png") -v, --verbose Enable verbose logging ``` ### Example ``` $ awsdac examples/alb-ec2.yaml ``` ``` $ awsdac privatelink.yaml -o custom-output.png ``` ### [Beta] Create a diagram from CloudFormation template `--cfn-template` option allows you to generate diagrams from CloudFormation templates, providing a visual representation of the resources. The tool can generate diagrams even if the CloudFormation template is not in a perfect format, enabling you to visualize the resources before actually creating the CloudFormation stack. This means you don't have to strictly adhere to the CloudFormation syntax constraints. > **NOTE:** The functionality of generating diagrams from CloudFormation templates is currently in beta. It sometimes works correctly, but we are aware of several known issues where the tool might not produce accurate results. We are actively working on improving the tool and fixing these issues. ``` $ awsdac examples/vpc-subnet-ec2-cfn.yaml --cfn-template ``` (generated from [the example of VPC,Subnet,EC2](examples/vpc-subnet-ec2-cfn.yaml)) <img src="examples/vpc-subnet-ec2-cfn.png" width="500"> There are some patterns where the tool may not work as expected. You can find a list of known issues and their status on the [issue tracker](https://github.com/awslabs/diagram-as-code/labels/cfn-template%20feature). Your feedback and issue reports are appreciated, as they will help enhance the tool's performance and accuracy. #### Use "--dac-file" option ``` $ awsdac examples/vpc-subnet-ec2-cfn.yaml --cfn-template --dac-file ``` CloudFormation templates have various dependencies, and there is no simple parent-child relationship between resources. As a result, generating the desired diagram directly from the existing CloudFormation template formats can be challenging at this stage. We considered utilizing Metadata or comments within the CloudFormation templates to include additional information. However, this approach would make the templates excessively long, and CloudFormation templates are primarily intended for resource creation and management rather than diagram generation. Additionally, combining different lifecycle components into a single CloudFormation template could make it difficult to manage and maintain. Therefore, instead of directly generating diagrams from CloudFormation templates, you can create a separate YAML file from CloudFormation template and customize this YAML file. This customized YAML file can then be used as input for `awsdac` to generate the desired architecture diagrams. By decoupling the diagram generation process from the CloudFormation template structure, this approach offers greater flexibility and customization while leveraging the specialized strengths of `awsdac`. ``` CloudFormation template --[awsdac]--> yaml file in awsdac format --[user custom]--> your desired diagram :) ``` ## Features - **Compliant with AWS architecture guidelines** Easily generate diagrams that follow [AWS diagram guidelines](https://aws.amazon.com/architecture/icons). - **Flexible** Automatically adjust the position and size of groups. - **Lightweight & CI/CD-friendly** Start quickly on a container; no dependency on headless browser or GUI. - **Integrate with your Infrastructure as Code** Generate diagrams to align with your IaC code without managing diagrams manually. - **As a drawing library** Use as Golang Library and integrate with other IaC tools, AI, or drawing GUI tools. - **Extensible** Add definition files to create non-AWS diagrams as well. ## Resource types See [doc/resource-types.md](doc/resource-types.md). ## Resource Link See [doc/links.md](doc/links.md). ## Security See [CONTRIBUTING](CONTRIBUTING.md#security-issue-notifications) for more information. ## License This project is licensed under the Apache-2.0 License. ", Assign "at most 3 tags" to the expected json: {"id":"8481","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"