Visual Infrastructure Design - Building Serverless Architectures Visually with AWS Infrastructure Composer (formerly AWS Application Composer)

Learn how to visually design serverless applications with AWS Infrastructure Composer. This article covers drag-and-drop architecture design and automatic SAM/CloudFormation template generation.

About 7 min readLast updated: 2026-10-30

The Challenge of IaC Templates and Infrastructure Composer

SAM and CloudFormation templates are powerful IaC tools, but writing YAML can be daunting for beginners, and understanding relationships between resources requires keeping the entire structure in your head. Serverless architectures in particular involve many interconnected resources such as Lambda, API Gateway, DynamoDB, S3, SQS, SNS, EventBridge, and Step Functions, making it difficult to grasp the overall template structure. AWS Infrastructure Composer is a tool that lets you design serverless application architectures on a visual canvas using drag and drop, automatically generating SAM/CloudFormation templates. The visual and code representations stay in bidirectional sync, so changes on the canvas are immediately reflected in the template, and manual template edits are reflected on the canvas.

Visual Design and Template Generation

Infrastructure Composer's canvas displays AWS serverless resources as cards. You drag and drop Lambda functions, API Gateway, DynamoDB tables, S3 buckets, SQS queues, SNS topics, EventBridge rules, and Step Functions state machines onto the canvas. When you connect resources with lines, the necessary IAM policies (such as read/write permissions from Lambda to DynamoDB), environment variables (table name references), and event source mappings (SQS to Lambda triggers) are automatically added to the template. Each resource's properties (Lambda runtime, memory size, DynamoDB key definitions, etc.) are configured by clicking on the card. Importing an existing SAM template expands its contents onto the visual canvas, giving you a visual overview of the entire architecture.

VS Code Integration and Workflow

Infrastructure Composer is provided as a VS Code extension (included in the AWS Toolkit), and the browser-based version in the AWS Management Console reaches end of support on December 7, 2026. Infrastructure Composer stopped accepting new customers on October 29, 2026 (as of October 2026). The VS Code version lets you directly edit templates on your local file system, switching between the visual canvas and code editor via tabs. An efficient workflow is to handle overall design visually and fine-tune detailed properties in the code editor. The generated templates can be deployed directly with SAM CLI. Running sam build followed by sam deploy provisions the visually designed architecture in your AWS environment. Infrastructure Composer is completely free; you only pay for the AWS resources that are provisioned.

Infrastructure Composer Pricing

Infrastructure Composer is free to use. There are no additional charges for the visual editor, automatic SAM template generation, or local file synchronization. It is also provided free as a VS Code extension. Costs are incurred only for the AWS resources (Lambda, API Gateway, DynamoDB, etc.) deployed using the generated templates.

Benefits of Visualization

When you manage infrastructure only with code, you need to read through the templates to grasp the overall configuration. A visual design tool displays resources and their relationships as a diagram, so you can understand the whole architecture at a glance. It helps members who newly join a project grasp the configuration quickly, and it also makes it easier to align understanding within the team. Because you can visually confirm which resources connect to which, you also notice gaps and errors in the design more easily. The value of visual design lies in the fact that you can combine the accuracy of code with the clarity of a diagram.

Round-Trip Editing with Code

The strength of a visual design tool is that you can move back and forth between editing in the diagram and editing in code. When you place and connect resources on the screen, the corresponding IaC template is generated automatically. Conversely, you can also load an existing template and visualize it as a diagram. This bidirectional integration lets you work flexibly, for example by assembling the overall structure visually and then adjusting the details in code. What the tool generates is a standard IaC template, so you can incorporate it into your existing deployment setup as is. What makes it practical is that you are not tied to either the diagram or the code and can use each according to the situation.

Use in Team Development and Reviews

Visual design shows its strength when a team designs and reviews together. If you share the architecture as a diagram, discussing the configuration becomes easier even among members with different technical backgrounds. In design reviews, you can check for missing or excess resources and the validity of connections while looking at the diagram. You can also use the diagram as design documentation as it is, which helps with recording and sharing the configuration. If you combine it with code reviews, you can verify the design from both the accuracy of the details and the validity of the whole. Communication through a shared diagram aligns the team's understanding and raises design quality.

Scope and Limitations

A visual design tool is not all-purpose; it has areas where it excels. It is suited to assembling serverless architectures and architectures up to a certain scale, and you can give them shape quickly. On the other hand, for very complex, large-scale infrastructure or advanced templates that make heavy use of fine-grained conditional branches and loops, writing directly in code is easier to handle in some cases. A practical division of roles is to design the overall structure visually and supplement the complex parts with code. If you understand the range where the tool excels and combine it with management through code, you can secure both design efficiency and expressiveness.

Summary - Guidelines for Using Infrastructure Composer

AWS Infrastructure Composer is a tool that enables visual design of serverless architectures and automatic SAM template generation. Its key strengths are intuitive drag-and-drop design, bidirectional sync between visual and code, and automatic IAM policy generation. It is ideal for learning serverless architectures, prototyping new projects, and sharing and reviewing architectures within teams. It is free to use and integrates into your daily development workflow through VS Code.

References (Official AWS Resources)

The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.

If this page and the official documentation disagree, treat the official documentation as authoritative.

How AI-DLC Transforms Software Development - A Practical Guide to the Inception, Construction, and Operation PhasesAn overview of the AI-DLC methodology that places AI at the center of the development process. Learn about the three phases of Inception, Construction, and Operation, and how to put them into practice with Kiro and Amazon Q Developer.Hands-On with the AI-DLC Unicorn Gym Workshop - Learning AI-DLC Through Team DevelopmentA complete look at the hands-on workshop where you experience AI-DLC through three days of team development. Learn how to run Mob Elaboration and Mob Construction, and how to leverage open-source workflows.Visually Design Serverless Applications with AWS Infrastructure Composer (formerly AWS Application Composer) - Automatic IaC Template GenerationThis article explains visual design of serverless architectures with Infrastructure Composer, automatic SAM template generation, and VS Code integration.Artifact Repository Management - Building a Secure Package Management Platform with AWS CodeArtifactLearn how to build and operate an artifact repository using AWS CodeArtifact. This guide covers centralizing package management for npm, Maven, PyPI, and more, along with building secure build pipelines through CodeBuild integration.How AWS API Throttling Works - The Token Bucket Algorithm and the Truth Behind 429 ErrorsLearn how AWS API rate limiting is implemented using the token bucket algorithm, understand the concept of burst capacity, explore differences in throttling limits across services, and discover practical strategies to avoid throttling.Why AWS APIs Return XML - The Evolution from Query APIs to REST JSONExplore the historical reasons why S3 and EC2 APIs return XML responses, the differences between Query APIs and REST APIs, the evolution of authentication from Signature V2 to V4, and the complexity that SDKs abstract away.Why AWS API Endpoints Differ by Region - The Design of Global and Regional ServicesWe explain the design reasons behind the separation of regional endpoints like ec2.us-east-1.amazonaws.com and global endpoints like iam.amazonaws.com, as well as the existence of dual-stack and FIPS endpoints.Browser-Based Shell Environment - Instant CLI Access with AWS CloudShellExplains the browser-based shell environment powered by AWS CloudShell. Covers the CLI environment available instantly from the AWS Management Console, pre-installed development tools, automatic IAM authentication integration, secure file management, and practical tips for improving operational efficiency.