Choose and maintain a workload

Select what belongs together

Use Add workload → AWS → discovered resources. Search for a known resource and choose the supporting resources it depends on. AWS resource-type filters show only available types, with counts. Keep one business capability together rather than selecting a whole account because it is convenient.

The selector normally hides resources already assigned to another workload. Enable Show resources used by other workloads when you need to inspect a shared dependency.

Validate the map

Open Workload map. Select a resource to see its identity and discovery evidence. A line labelled “can write to” means configuration and permission support a write; it does not mean a write was observed.

A resource without a line may be unconnected, outside a supported relationship pattern or missing evidence. Check with the application owner. Resolve any question that prevents the test you need.

Keep the application outcome stable

The target can merge or split source resources. A source API Gateway and several functions do not have to become identical target resources. Define the API result or completed processing outcome that customers and other systems rely on.

Internal component checks help diagnose problems. They should not become accidental requirements to reproduce the source architecture.

What about network-only workloads?

A subnet and route table can have infrastructure requirements without application compute. Select the discovered properties that matter, such as minimum address capacity. A configuration test cannot establish real connectivity, firewall equivalence or traffic flow. Those need deeper configuration review or active testing.

Change the selection

Open Workload options → Add or remove resources. Saving creates a new workload revision. Earlier test results still describe their earlier revision. Review checks and test material after changes; a check attached to a removed interface needs attention before it can contribute to a new proof.

A fresh AWS discovery supplies new inventory. The current product does not automatically reconcile every AWS-side change into your selected workload.

Archive a workload

Use Workload options → Archive workload. Archiving stops monitoring and removes the workload from the active project. Existing evidence is retained in the audit record. It does not delete AWS resources. An active test must finish before the workload can be archived.

Archiving is not complete erasure. Ask about data deletion and backup expiry separately before treating it as a deletion request.