Compute environments on Fargate
AWS Batch compute environments on AWS Fargate don't support all of the compute environment parameters that are available. Some parameters are not supported at all. Others have specific requirements for Fargate.
The following list describes compute environment parameters that aren't valid or otherwise restricted in Fargate jobs.
type-
This parameter must be
MANAGED."type": "MANAGED" - Parameters in the
computeResourcesobject -
allocationStrategybidPercentagedesiredvCpusimageIdinstanceTypesec2Configurationec2KeyPairinstanceRolelaunchTemplateminvCpusplacementGroupspotIamFleetRole-
These aren't applicable for Fargate compute environments and can't be provided.
subnets-
If the subnets listed in this parameter don't have NAT gateways attached, the
assignPublicIpparameter in the job definition must be set toENABLED. tags-
This isn't applicable for Fargate compute environments and can't be provided. To specify tags for Fargate compute environments, use the
tagsparameter that's not in thecomputeResourcesobject. type-
This must be either
FARGATEorFARGATE_SPOT."type": "FARGATE_SPOT"