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

# aws_pcs_compute_node_group{% #aws_pcs_compute_node_group %}

## `account_id`{% #account_id %}

**Type**: `STRING`

## `ami_id`{% #ami_id %}

**Type**: `STRING`**Provider name**: `amiId`**Description**: The ID of the Amazon Machine Image (AMI) that Amazon Web Services PCS uses to launch instances. If not provided, Amazon Web Services PCS uses the AMI ID specified in the custom launch template.

## `arn`{% #arn %}

**Type**: `STRING`**Provider name**: `arn`**Description**: The unique Amazon Resource Name (ARN) of the compute node group.

## `cluster_id`{% #cluster_id %}

**Type**: `STRING`**Provider name**: `clusterId`**Description**: The ID of the cluster of the compute node group.

## `created_at`{% #created_at %}

**Type**: `TIMESTAMP`**Provider name**: `createdAt`**Description**: The date and time the resource was created.

## `custom_launch_template`{% #custom_launch_template %}

**Type**: `STRUCT`**Provider name**: `customLaunchTemplate`

- `id`**Type**: `STRING`**Provider name**: `id`**Description**: The ID of the EC2 launch template to use to provision instances. Example: `lt-xxxx`
- `version`**Type**: `STRING`**Provider name**: `version`**Description**: The version of the EC2 launch template to use to provision instances.

## `error_info`{% #error_info %}

**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `errorInfo`**Description**: The list of errors that occurred during compute node group provisioning.

- `code`**Type**: `STRING`**Provider name**: `code`**Description**: The short-form error code.
- `message`**Type**: `STRING`**Provider name**: `message`**Description**: The detailed error information.

## `iam_instance_profile_arn`{% #iam_instance_profile_arn %}

**Type**: `STRING`**Provider name**: `iamInstanceProfileArn`**Description**: The Amazon Resource Name (ARN) of the IAM instance profile used to pass an IAM role when launching EC2 instances. The role contained in your instance profile must have the `pcs:RegisterComputeNodeGroupInstance` permission. The resource identifier of the ARN must start with `AWSPCS` or it must have `/aws-pcs/` in its path.
Examples
- `arn:aws:iam::111122223333:instance-profile/AWSPCS-example-role-1`
- `arn:aws:iam::111122223333:instance-profile/aws-pcs/example-role-2`



## `id`{% #id %}

**Type**: `STRING`**Provider name**: `id`**Description**: The generated unique ID of the compute node group.

## `instance_configs`{% #instance_configs %}

**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `instanceConfigs`**Description**: A list of EC2 instance configurations that Amazon Web Services PCS can provision in the compute node group.

- `instance_type`**Type**: `STRING`**Provider name**: `instanceType`**Description**: The EC2 instance type that Amazon Web Services PCS can provision in the compute node group. Example: `t2.xlarge`

## `modified_at`{% #modified_at %}

**Type**: `TIMESTAMP`**Provider name**: `modifiedAt`**Description**: The date and time the resource was modified.

## `name`{% #name %}

**Type**: `STRING`**Provider name**: `name`**Description**: The name that identifies the compute node group.

## `purchase_option`{% #purchase_option %}

**Type**: `STRING`**Provider name**: `purchaseOption`**Description**: Specifies how EC2 instances are purchased on your behalf. Amazon Web Services PCS supports On-Demand and Spot instances. For more information, see [Instance purchasing options](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-purchasing-options.html) in the Amazon Elastic Compute Cloud User Guide. If you don't provide this option, it defaults to On-Demand.

## `scaling_configuration`{% #scaling_configuration %}

**Type**: `STRUCT`**Provider name**: `scalingConfiguration`

- `max_instance_count`**Type**: `INT32`**Provider name**: `maxInstanceCount`**Description**: The upper bound of the number of instances allowed in the compute fleet.
- `min_instance_count`**Type**: `INT32`**Provider name**: `minInstanceCount`**Description**: The lower bound of the number of instances allowed in the compute fleet.

## `slurm_configuration`{% #slurm_configuration %}

**Type**: `STRUCT`**Provider name**: `slurmConfiguration`

- `slurm_custom_settings`**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `slurmCustomSettings`**Description**: Additional Slurm-specific configuration that directly maps to Slurm settings.
  - `parameter_name`**Type**: `STRING`**Provider name**: `parameterName`**Description**: Amazon Web Services PCS supports configuration of the following Slurm parameters:
    - For clusters
      - [`Prolog`](https://slurm.schedmd.com/slurm.conf.html#OPT_Prolog_1)
      - [`Epilog`](https://slurm.schedmd.com/slurm.conf.html#OPT_Epilog_1)
      - [`SelectTypeParameters`](https://slurm.schedmd.com/slurm.conf.html#OPT_SelectTypeParameters)
    - For compute node groups
      - [`Weight`](https://slurm.schedmd.com/slurm.conf.html#OPT_Weight)
      - [`RealMemory`](https://slurm.schedmd.com/slurm.conf.html#OPT_Weight)
  - `parameter_value`**Type**: `STRING`**Provider name**: `parameterValue`**Description**: The values for the configured Slurm settings.

## `spot_options`{% #spot_options %}

**Type**: `STRUCT`**Provider name**: `spotOptions`

- `allocation_strategy`**Type**: `STRING`**Provider name**: `allocationStrategy`**Description**: The Amazon EC2 allocation strategy Amazon Web Services PCS uses to provision EC2 instances. Amazon Web Services PCS supports lowest price, capacity optimized, and price capacity optimized. For more information, see [Use allocation strategies to determine how EC2 Fleet or Spot Fleet fulfills Spot and On-Demand capacity](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet-allocation-strategy.html) in the Amazon Elastic Compute Cloud User Guide. If you don't provide this option, it defaults to price capacity optimized.

## `status`{% #status %}

**Type**: `STRING`**Provider name**: `status`**Description**: The provisioning status of the compute node group.The provisioning status doesn't indicate the overall health of the compute node group.

## `subnet_ids`{% #subnet_ids %}

**Type**: `UNORDERED_LIST_STRING`**Provider name**: `subnetIds`**Description**: The list of subnet IDs where instances are provisioned by the compute node group. The subnets must be in the same VPC as the cluster.

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`