AWS resource reference
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.
In Atlas
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.
Use editor controls for selection, inspector drafts and action menus. Creating or editing this design data does not create an AWS resource.
Worked example: a two-zone public application balancer
A typical AWS chain is listener → forwarding action → target group → registered targets, with health checks at the target group. Atlas can represent that data, including in a demo design, but representation is not proof of full public editor authoring support.
- Create a VPC and two Public subnets with different valid account-region AZs. For example, in eu-west-2 use eu-west-2a and eu-west-2b. These are design examples, not an account availability guarantee.
- Select a compatible subnet and execute Add New Load Balancer. The placement initializer selects compatible subnet data; creation reports missing/invalid prerequisites instead of silently creating a whole network.
- Inspect the balancer. Keep Variant Application and Scheme InternetFacing. In Subnets select one Public subnet per AZ in this VPC. Apply to commit the draft.
- Reopen the inspector to inspect Listeners and any owned data-only records. Existing listener fields can be read/edited where shown. A newly added listener has required Default Actions but the current generic editor has no action-creation controls; do not treat adding a port as a finished forwarding configuration.
- Read Listener, TargetGroup and HealthCheck to understand existing data and AWS meaning. Save the committed design. No listener or traffic service has been deployed to AWS.
Fields and editing
| Field / label | Meaning and behaviour | Defaults and constraints |
|---|---|---|
| VPC Parent | Atlas reference to VPC; canonical resource ID, not an AWS ID. Read-only ownership. | Required. |
| Variant | Editable kind of load balancer. | Application (bare default), Network, Gateway. |
| Scheme | Editable exposure model; constrains eligible subnet associations. | InternetFacing (bare default) uses Public subnets; Internal uses Private subnets. |
| Subnets | Atlas reference to Subnet; canonical resource ID, not an AWS ID. Dedicated multiple selector; same VPC, matching account region, one subnet per AZ. | Application needs at least two distinct AZs; other variants at least one. Interactive creation needs a second compatible subnet. |
| Security Groups | Atlas reference to Security Group; canonical resource ID, not an AWS ID. Associated security-group data. | Bare default empty; interactive creation may create a data-only group. |
| Listeners | Inline create/remove child records; scalar listener details can be edited. | Bare default empty. See Listener for required-action authoring limitation. |
| Deletion Protection Enabled | Editable design boolean. Not a substitute for the Atlas delete action’s own validation. | Bare default false. |
AWS reference
Official AWS service guide explains the service. AWS property reference is a comparison reference. Atlas is an offline design model; its fields are not a promise of direct AWS API/CloudFormation equivalence or regional availability.