Design. Understand. Deploy
Your guide to Atlas.
From your first deployment to the details of every cloud resource. Learn the platform and build your design in the desktop or WebGL editor.
Start here
Platform workflows
Sign in, sessions and sign out
Use the configured identity flow, return safely to Atlas and understand session limits.
Organisations and onboarding
Create or switch an organisation and understand organisation-wide access.
Create and manage deployments
Find designs, edit their details, open the editor, manage access and delete a saved deployment.
Invitations and members
Invite people, accept with the right identity and change membership safely.
Editor workflows
Save, Load Latest and unsaved work
Persist a design, reconstruct the latest saved snapshot and understand what is not version history.
Editor controls and inspector
Exact keyboard/mouse controls for the WebGL and desktop editor, including draft and delete behaviour.
Ownership, placement and resource IDs
Keep cloud ownership, visual hosting and cross-resource associations distinct.
AWS resource reference
Supporting data and reference types
Understand reference destinations and nested attachment data that have no public physical creation prefab.
AWS Account
The root of an AWS design. Create AWS Account is available from the global menu while no account exists.
VPC
A virtual network owned by an AWS Account. VPC is the canonical owner of the network resources placed within its subnets.
Subnet: public, private and database
All three subnet appearances share one resource type. Classification influences placement, defaults and eligible resource associations.
Internet Gateway
An internet gateway association belongs with a VPC design; it does not itself make every subnet internet-accessible.
NAT Gateway
A NAT design is VPC-owned and visually hosted on a subnet. A Public NAT requires the VPC’s internet gateway.
Route Table
A VPC-owned collection of routes with subnet associations. It is physically placed from a subnet action.
Route
Panel-only route data in a Route Table. A route destination identifies its entry; the current generic panel does not expose a full target-object editor.
EC2 instance
A VPC-owned compute design placed on a subnet. An image label is design text; Atlas does not resolve it into an AMI or start an instance.
Load Balancer
A VPC-owned load-balancer design with subnet associations and embedded listeners. Its panels do not currently provide a complete target-group/health-check authoring workflow.
LoadBalancerListener
Panel-only listener data within a Load Balancer. Existing actions/rules may be displayed, but the current generic collection UI cannot create them.
TargetGroup
Data-only target group owned by a Load Balancer. It has no physical prefab or public create action; the balancer’s owned-data section lists/removes records but does not open a full target-group editor.
HealthCheck
Panel-only health-check data belonging to a TargetGroup. These fields explain saved/demo data; the current public editor does not expose a complete TargetGroup/HealthCheck editing workflow.
RDS
A VPC-owned relational database design. Create it on a Database subnet after preparing a valid DB subnet group across at least two AZs.
RDS DB subnet group
A managed data-only VPC resource, not a physical prefab. Open Manage DB subnet groups from VPC or RDS.
RdsBackupConfig
Editable inline backup policy inside the RDS inspector. Settings describe desired backup behaviour, not backups already created in AWS.
RdsNetworkConfig
Editable inline network settings inside RDS. DB subnet group and security-group references are on the parent RDS resource.
Security Group
A VPC-owned traffic-policy design with ingress and egress rule collections. Atlas does not install a live firewall.
SecurityRule
Panel-only rule data inside a Security Group. Scalar rows are editable; Peer is a complex summary rather than a full public peer editor.