Arcentry for Amazon Web Services
Turn your Amazon Web Services infrastructure into a diagram your team can explore. Map services, VPCs, and application dependencies in 2D or 3D, then share a clear view for design reviews, documentation, and operations.
An AWS architecture diagram should help someone answer a question: where does a request go, what depends on this database, or which services share a network boundary? Arcentry gives you a visual canvas for those conversations, with AWS components, editable connections, labels, and areas for grouping infrastructure.
Create an overview for a design review, then add detail where it matters. An application team might need to see API calls and queues; an operations team might need availability zones, load balancers, and database dependencies. You can present the architecture in 2D or use an isometric 3D view to make groups and relationships easier to explore.
Group resources by the scope you need to explain: accounts, regions, availability zones, VPCs, or subnets. Label each boundary and distinguish network placement from logical dependencies. A managed service can be connected to a workload without being drawn as a server inside its subnet.
Use named connections to explain HTTP requests, messages, and data movement. Include the open-source services and external APIs around your AWS deployment so the diagram reflects the system your team works with, rather than an isolated collection of cloud icons.
Share an image in a proposal or embed an interactive diagram in documentation. When your infrastructure changes, edit the diagram or update it through Arcentry’s REST API. Charts and metadata can add context to the places where your team needs it.
Arcentry is listed among the drawing and diagramming tools on the AWS architecture-icons page. Build your first AWS diagram on the free plan, and explore plans and limits as your documentation grows.
Architecture ideas
Use these architecture patterns to decide what your AWS diagram needs to communicate: the request path, event flow, or relationship between workloads and networks.
Trace a request from Route 53 and CloudFront through a load balancer to application servers and Amazon RDS. Mark VPC and subnet boundaries, and distinguish public entry points from private application and database resources.
Connect API Gateway, Lambda, and DynamoDB, then show the queues or event sources that trigger background work. Label synchronous calls separately from asynchronous messages so readers can follow the flow and discuss failure handling.
Show an ECS or EKS workload, its load balancer, and its database dependencies. Group resources by availability zone where it helps explain resilience, and keep cluster-level connections distinct from the details of individual services.
From design to documentation
Place AWS components by hand, describe your system with AI Chat, or generate a diagram from a CloudFormation template or exported Terraform/OpenTofu JSON. Review the result against the architecture you want to explain.
Group resources into regions, availability zones, and VPCs as needed. Add directional connections, service names, and annotations so a reader understands what runs where and how the parts communicate.
Export an image for a design document or publish an interactive embed. Use Arcentry's REST API to update diagram objects and connect operational context supplied by your own tools.
Good to know
Have a question about your workflow? Write to info@arcentry.com.
Pair your diagram with the provider's technical guidance.
Yes. Arcentry has a free plan with no credit card required. You can build your first AWS diagram and explore the editor before choosing a paid plan. See the pricing section for current limits.
Yes. Arcentry supports CloudFormation import and Terraform/OpenTofu JSON exported with terraform show -json or tofu show -json. Check the generated components and connections, then refine the diagram for the audience and level of detail you need.
Yes. Combine AWS components with other cloud providers, Kubernetes, open-source services, and custom components on the same canvas. This is useful for hybrid networks, migrations, and applications with dependencies outside AWS.
Arcentry supports charts, status indicators, and programmable diagram updates. Use the REST API to send selected metrics or state from your monitoring workflow into the diagram, so the architecture and its operational context can be viewed together.
Make the system visible
Start with the workload your team needs to understand, then build the diagram around it.