Choose and configure services.
Search the AWS catalog, add supported services, and edit properties such as Lambda runtime, memory, and timeout.
Open-source AWS architecture workspace
Design the architecture.
Understand the details.
Cloud Markup brings AWS services, configuration, connections, and validation into one visual workspace. Make design decisions with the model in view.
Already have an account? Sign in. Registration follows current beta availability.
Inside the actual application
One design. Connected decisions.
The Atlas Commerce reference example brings ingress, processing, messaging and data decisions into one visual model. Explore it as a synthetic design in progress.
A synthetic architecture model. These screenshots show design activity; they do not show deployed resources or live order processing.
What you can do
Bring the questions
closer to the canvas.
Configure resources and understand what each connection means before carrying the design forward.
Review the relationship.
Inspect connection requirements, permissions, and delivery guidance before applying a typed relationship.
Keep findings visible.
Run supported checks and inspect the exact finding against the affected resources. An unresolved question stays part of the review.
Interactive illustration
Open a service.
Explore the decisions.
An illustrated guide to the EventBridge Order Pipeline example. Select a service to inspect its configuration and relationships.
Marketing illustration based on the demo model. This explores static explanations; it does not run the application or deploy cloud resources.
The example at a glance
An IAM execution role is assigned to a Lambda function. The function publishes to an EventBridge event bus and sends messages to an SQS queue.
- IAM execution role
- Represents the permissions the function needs. Connection review explains intended access.
- Lambda function
- Node.js 24, ten-second timeout, 512 MB memory. Its stated purpose is to route synthetic order events.
- EventBridge event bus
- The Lambda publisher uses the intended events:PutEvents permission on the connected bus. Delivery guidance includes possible duplicate events.
- SQS queue
- The model includes a Lambda-to-queue relationship for fulfillment work. Review the selected connection's requirements in the application.
Select a service with a click or Enter. Arrow keys move between services. Escape returns to the overview.
One model, three relationships. Explore the permissions, settings, and delivery questions behind the diagram.
Service details
Permissions in the model
The execution role is assigned to the Lambda function. Review the access required by its connected services alongside the architecture.
Connection context
- The EventBridge relationship describes the intended
events:PutEventspermission on the connected bus. - The model records intended access; this illustration does not create an IAM policy or role.
Configuration from the example
- Function name
- atlas-order-router
- Runtime
- Node.js 24
- Timeout
- 10 seconds
- Memory
- 512 MB
Purpose and relationships
Publish synthetic order events to EventBridge and enqueue fulfillment work in SQS. The application provides an explicit manual purpose preview before applying changes.
A stated design purpose is not evidence of generated code or a deployed workload.
Typed relationship
The Lambda publisher connects to the EventBridge event bus. Connection review shows the intended event-publication permission before the relationship is applied.
Questions to carry into review
- Intended permission:
events:PutEventson the connected bus. - Delivery guidance: at least once; duplicate events are possible.
- The captured validation warning leaves regional availability unverified.
Work waiting to be handled
The model connects the Lambda function to an SQS queue for synthetic fulfillment work. The queue is a separate resource with its own configuration.
Review the selected relationship
Inspect the connection requirements and intended permissions in the app, then review findings against the model. This illustration shows design intent; no messages are sent.
Regional availability remains an open question in the captured validation run.
Design to handoff
A deliberate path
through the details.
Design, configure, connect, validate, review, then export where your workspace supports it. CloudFormation is the current export target; access and workload coverage vary in beta.
- 01
Design
Add supported AWS resources.
- 02
Configure
Set properties and purpose.
- 03
Connect
Review typed relationships.
- 04
Validate
Run checks and read findings.
- 05
Review
Resolve or document open questions.
- 06
Export
Where available, review a saved revision's output.
Open source · Apache 2.0
Explore the code.
Follow the project.
CloudMarkup's application source is public under the Apache License 2.0. Browse CloudMarkup-App for source, local setup guides and contribution guidance.
View CloudMarkup-App on GitHubThe public source and hosted beta have separate release cycles. Local setup does not enable hosted services or paid integrations.
See the roadmap, including AzureChoose your starting point
Explore the workspace.
Read the source.
Try the hosted beta, or follow the public local setup guides. Availability differs by environment.