---
title: Getting Started with Datadog
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Infrastructure > Datadog Resource Catalog
---

# aws_batch_job_queue{% #aws_batch_job_queue %}

## `account_id`{% #account_id %}

**Type**: `STRING`

## `compute_environment_order`{% #compute_environment_order %}

**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `computeEnvironmentOrder`**Description**: The compute environments that are attached to the job queue and the order that job placement is preferred. Compute environments are selected for job placement in ascending order.

- `compute_environment`**Type**: `STRING`**Provider name**: `computeEnvironment`**Description**: The Amazon Resource Name (ARN) of the compute environment.
- `order`**Type**: `INT32`**Provider name**: `order`**Description**: 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.

## `job_queue_arn`{% #job_queue_arn %}

**Type**: `STRING`**Provider name**: `jobQueueArn`**Description**: The Amazon Resource Name (ARN) of the job queue.

## `job_queue_name`{% #job_queue_name %}

**Type**: `STRING`**Provider name**: `jobQueueName`**Description**: The job queue name.

## `job_state_time_limit_actions`{% #job_state_time_limit_actions %}

**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `jobStateTimeLimitActions`**Description**: The set of actions that Batch perform on jobs that remain at the head of the job queue in the specified state longer than specified times. Batch will perform each action after `maxTimeSeconds` has passed.

- `action`**Type**: `STRING`**Provider name**: `action`**Description**: The action to take when a job is at the head of the job queue in the specified state for the specified period of time. The only supported value is `CANCEL`, which will cancel the job.
- `max_time_seconds`**Type**: `INT32`**Provider name**: `maxTimeSeconds`**Description**: The approximate amount of time, in seconds, that must pass with the job in the specified state before the action is taken. The minimum value is 600 (10 minutes) and the maximum value is 86,400 (24 hours).
- `reason`**Type**: `STRING`**Provider name**: `reason`**Description**: The reason to log for the action being taken.
- `state`**Type**: `STRING`**Provider name**: `state`**Description**: The state of the job needed to trigger the action. The only supported value is `RUNNABLE`.

## `priority`{% #priority %}

**Type**: `INT32`**Provider name**: `priority`**Description**: The priority of the job queue. Job queue priority determines the order that job queues are evaluated when multiple queues dispatch jobs within a shared compute environment. A higher value for `priority` indicates a higher priority. Queues are evaluated in cycles, in descending order by priority. For example, a job queue with a priority value of `10` is evaluated before a queue with a priority value of `1`. All of the compute environments must be either Amazon EC2 (`EC2` or `SPOT`) or Fargate (`FARGATE` or `FARGATE_SPOT`). Amazon EC2 and Fargate compute environments can't be mixed.Job queue priority doesn't guarantee that a particular job executes before a job in a lower priority queue. Jobs added to higher priority queues during the queue evaluation cycle might not be evaluated until the next cycle. A job is dispatched from a queue only if resources are available when the queue is evaluated. If there are insufficient resources available at that time, the cycle proceeds to the next queue. This means that jobs added to higher priority queues might have to wait for jobs in multiple lower priority queues to complete before they are dispatched. You can use job dependencies to control the order for jobs from queues with different priorities. For more information, see [Job Dependencies](https://docs.aws.amazon.com/batch/latest/userguide/job_dependencies.html) in the Batch User Guide.

## `scheduling_policy_arn`{% #scheduling_policy_arn %}

**Type**: `STRING`**Provider name**: `schedulingPolicyArn`**Description**: The Amazon Resource Name (ARN) of the scheduling policy. The format is `aws: Partition :batch: Region : Account :scheduling-policy/ Name`. For example, `aws:aws:batch:us-west-2:123456789012:scheduling-policy/MySchedulingPolicy`.

## `state`{% #state %}

**Type**: `STRING`**Provider name**: `state`**Description**: Describes the ability of the queue to accept new jobs. If the job queue state is `ENABLED`, it can 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.

## `status`{% #status %}

**Type**: `STRING`**Provider name**: `status`**Description**: The status of the job queue (for example, `CREATING` or `VALID`).

## `status_reason`{% #status_reason %}

**Type**: `STRING`**Provider name**: `statusReason`**Description**: A short, human-readable string to provide additional details for the current status of the job queue.

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`