AWS Workload Runtime and Deployment

When to use

Invoke when choosing how a workload runs on AWS, designing its load balancing and autoscaling, or defining its deployment and rollback mechanics — within the network/identity foundation an environment already has.

Do not use for: AWS Organizations/account/SCP topology (use aws-account-and-organization-topology); VPC/IAM/KMS/Secrets foundation (use aws-network-and-identity-foundation); CloudWatch/cost instrumentation (use aws-observability-and-cost-readiness); multi-region/DR (use aws-dr-and-multi-region-readiness); in-cluster Kubernetes workload manifests when EKS is the substrate (the kubernetes Family G skills own those — this skill provisions the cluster substrate, not its workloads); IaC module/state/plan/apply mechanics (the terraform Family H skills).

Inputs

Required:

• A network/identity foundation from aws-network-and-identity-foundation (the VPC subnets, IAM roles, and CMKs the workload runs within).
• Approved infrastructure-platform.md Runtime Substrate Selection and Deployment & Release Architecture, or explicit confirmation they are intentionally deferred.

Optional: