As a user, I want to be able to provide multiple subnet IDs when configuring an AWS Cloud compute environment, so that I can spread workloads across multiple Availability Zones for resilience and spot capacity availability.
The AWS Cloud CE currently accepts only a single subnet ID (
subnetId
) at the API level, which flows through to both the UI (single string field) and the Terraform provider (
subnet_id
string attribute). This means users cannot configure multi-AZ deployments from the UI, API, or Terraform today.
By contrast, AWS Batch CEs (via forge config) already support
subnets: []string
in the API and a list attribute in Terraform. AWS Cloud CE should be brought to parity.