class Aws::Batch::Types::CreateJobQueueRequest

Contains the parameters for `CreateJobQueue`.

@note When making an API call, you may pass CreateJobQueueRequest

data as a hash:

    {
      job_queue_name: "String", # required
      state: "ENABLED", # accepts ENABLED, DISABLED
      priority: 1, # required
      compute_environment_order: [ # required
        {
          order: 1, # required
          compute_environment: "String", # required
        },
      ],
      tags: {
        "TagKey" => "TagValue",
      },
    }

@!attribute [rw] job_queue_name

The name of the job queue. Up to 128 letters (uppercase and
lowercase), numbers, and underscores are allowed.
@return [String]

@!attribute [rw] state

The state of the job queue. If the job queue state is `ENABLED`, it
is able to accept jobs. If the job queue state is `DISABLED`, new
jobs can't be added to the queue, but jobs already in the queue can
finish.
@return [String]

@!attribute [rw] priority

The priority of the job queue. Job queues with a higher priority (or
a higher integer value for the `priority` parameter) are evaluated
first when associated with the same compute environment. Priority is
determined in descending order. For example, a job queue with a
priority value of `10` is given scheduling preference over a job
queue with a priority value of `1`. 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.
@return [Integer]

@!attribute [rw] compute_environment_order

The set of compute environments mapped to a job queue and their
order relative to each other. The job scheduler uses this parameter
to determine which compute environment should run a specific job.
Compute environments must be in the `VALID` state before you can
associate them with a job queue. You can associate up to three
compute environments 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 markdown="1"> All compute environments that are associated with a job queue must
share the same architecture. Batch doesn't support mixing compute
environment architecture types in a single job queue.

 </note>
@return [Array<Types::ComputeEnvironmentOrder>]

@!attribute [rw] tags

The tags that you apply to the job queue to help you categorize and
organize your resources. Each tag consists of a key and an optional
value. For more information, see [Tagging your Batch resources][1]
in *Batch User Guide*.

[1]: https://docs.aws.amazon.com/batch/latest/userguide/using-tags.html
@return [Hash<String,String>]

@see docs.aws.amazon.com/goto/WebAPI/batch-2016-08-10/CreateJobQueueRequest AWS API Documentation

Constants

SENSITIVE