AWS::Batch::JobQueue ComputeEnvironmentOrder - Amazon CloudFormation
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

AWS::Batch::JobQueue ComputeEnvironmentOrder

The order in which compute environments are tried for job placement within a queue. Compute environments are tried in ascending order. For example, if two compute environments are associated with a job queue, the compute environment with a lower order integer value is tried for job placement first. Compute environments must be in the VALID state before you can associate them with a job queue. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT); EC2 and Fargate compute environments can't be mixed.

Note

All compute environments that are associated with a job queue must share the same architecture. Amazon Batch doesn't support mixing compute environment architecture types in a single job queue.

Syntax

To declare this entity in your Amazon CloudFormation template, use the following syntax:

JSON

{ "ComputeEnvironment" : String, "Order" : Integer }

YAML

ComputeEnvironment: String Order: Integer

Properties

ComputeEnvironment

The Amazon Resource Name (ARN) of the compute environment.

Required: Yes

Type: String

Update requires: No interruption

Order

The order of the compute environment. Compute environments are tried in ascending order. For example, if two compute environments are associated with a job queue, the compute environment with a lower order integer value is tried for job placement first.

Required: Yes

Type: Integer

Update requires: No interruption