# Install awsdac with Homebrew CLI tool for drawing AWS architecture. Version 0.23 via Homebrew; verified 2026-07-30. ## Install ```sh sudo av install brew:awsdac ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install awsdac ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:awsdac - **Package manager:** Homebrew - **Version:** 0.23 - **Source summary:** CLI tool for drawing AWS architecture - **Homepage:** - **Repository:** - **Last updated:** 2026-07-30T12:47:52Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - awsdac (alias) - awsdac-mcp-server (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.23 ## Project history and usage awsdac is the command-line interface for AWS Labs' Diagram-as-code project, a YAML-driven tool for drawing AWS architecture diagrams without a browser or heavyweight image pipeline. ### Project history The `awslabs/diagram-as-code` repository was created in February 2024 and began publishing 0.x releases almost immediately. Its README presents the project as a way to manage diagrams with Git, write human-readable YAML, and generate AWS architecture diagrams that follow AWS diagram guidelines. The project later expanded beyond a single CLI into a Go library and `awsdac-mcp-server`, with documentation for CloudFormation conversion, templating, resource definitions, links, and AI assistant integration. ### Adoption history awsdac's adoption is early but visible for a young AWS Labs tool: the repository is under the official `awslabs` organization, has Homebrew packaging, and has accumulated public GitHub attention since 2024. It fits the broader infrastructure-as-code habit of keeping generated artifacts and their source definitions in version control. The tool targets teams that want architecture diagrams to live beside IaC and documentation, rather than in manually edited drawing files. ### How it is used Users install with `go install github.com/awslabs/diagram-as-code/cmd/awsdac@latest` or `brew install awsdac`, then run `awsdac ` to render YAML into an output image. Flags cover output filenames, templates, CloudFormation conversion, and definition-file overrides. Because it draws from declarative YAML rather than cloud credentials, no AWS credentials file is documented as required for normal diagram generation. ### Why package nerds care awsdac is a package-manager-friendly example of documentation automation: one CLI turns versioned text into visual architecture diagrams. For package nerds, its appeal is that the rendering tool can be pinned in CI and used without a GUI, headless browser, or SaaS diagram editor. Its presence in Homebrew also shows how AWS Labs experiments can move quickly into developer workstation tooling when they are delivered as a single Go CLI. ### Timeline - 2024: Public GitHub repository `awslabs/diagram-as-code` created. - 2024: v0.10 release published. - 2024: v0.21.x releases expand the early 0.x line. - 2026: v0.23 release published with additional diagram features. ### Related projects - AWS Architecture Icons and guidelines provide the visual vocabulary referenced by the project. - Infrastructure-as-code tools such as CloudFormation are adjacent inputs; the project documents beta CloudFormation conversion. - MCP integrations are exposed by the `awsdac-mcp-server` executable. ### Sources - - - - - ## Security Notes broad file, network, media, or database tool signal. - **Geiger risk:** blue / medium - broad file, network, media, or database tool signal ## Combined YAML source View the package source record on GitHub. [combined/awsdac.yml](https://github.com/mxcl/pkgdb/blob/main/combined/awsdac.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph