Editor workflows
Ownership, placement and resource IDs
Keep cloud ownership, visual hosting and cross-resource associations distinct.
Three different relationships
| Concept | Example | Effect |
|---|---|---|
| Cloud ownership | VPC belongs to an AWS Account; EC2 belongs to a VPC. | Canonical cloud hierarchy. Parent fields are read-only summaries in the generic inspector. |
| Atlas visual placement | An EC2, NAT Gateway, Route Table, Load Balancer or RDS appears on a Subnet. | Controls the Atlas scene host. It does not make the subnet the cloud owner. |
| Association or dependency | A balancer references subnets; RDS references a DB subnet group; a NAT depends on an Internet Gateway. | Represents network/configuration relationships and creation/validation prerequisites, separate from position. |
Canonical IDs, display IDs and AWS IDs
Each Atlas resource has a canonical Id: a 32-character GUID in N form, without hyphens. Cross-resource relationships store that canonical ID. Name is a human label and may be duplicated. Reference labels prefer the name; unnamed or duplicate-name entries append a short ID, normally 8 characters and extended to 12 for a short-ID collision. A short display ID is not the complete relationship value.
AWS Account ID is a separate 12-digit account-number field. Image ID, external route IDs, certificate identifiers and other AWS physical IDs/ARNs are distinct from canonical Atlas resource IDs. Do not paste an AWS ARN into a field that expects an Atlas ID or edit a shared Id to rename a resource.
Selectors may show missing/stale/unavailable targets. Missing, invalid or duplicate identities do not become valid by rendering a label. An unresolved selected ID remains visible for inspection, but is not a valid new candidate; no silent repair is implied. Inspect the target type, VPC/region, classification and AZ constraints and correct only through supported controls.
Reference destination guide
AWS Account, VPC, Subnet, Internet Gateway, Security Group, Load Balancer, TargetGroup and DB subnet group have dedicated guides. Data-only or unexposed destinations including Elastic IP, IAM roles/profiles, KMS keys, certificates, network interfaces and volumes are explained in supporting resource references.