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

# aws_medialive_node{% #aws_medialive_node %}

## `account_id`{% #account_id %}

**Type**: `STRING`

## `arn`{% #arn %}

**Type**: `STRING`**Provider name**: `Arn`**Description**: The ARN of the Node. It is automatically assigned when the Node is created.

## `channel_placement_groups`{% #channel_placement_groups %}

**Type**: `UNORDERED_LIST_STRING`**Provider name**: `ChannelPlacementGroups`**Description**: An array of IDs. Each ID is one ChannelPlacementGroup that is associated with this Node. Empty if the Node is not yet associated with any groups.

## `cluster_id`{% #cluster_id %}

**Type**: `STRING`**Provider name**: `ClusterId`**Description**: The ID of the Cluster that the Node belongs to.

## `connection_state`{% #connection_state %}

**Type**: `STRING`**Provider name**: `ConnectionState`**Description**: The current connection state of the Node.

## `id`{% #id %}

**Type**: `STRING`**Provider name**: `Id`**Description**: The unique ID of the Node. Unique in the Cluster. The ID is the resource-id portion of the ARN.

## `instance_arn`{% #instance_arn %}

**Type**: `STRING`**Provider name**: `InstanceArn`**Description**: The EC2 ARN of the Instance associated with the Node.

## `managed_instance_id`{% #managed_instance_id %}

**Type**: `STRING`**Provider name**: `ManagedInstanceId`**Description**: At the routing layer will get it from the callerId/context for use with bring your own device.

## `name`{% #name %}

**Type**: `STRING`**Provider name**: `Name`**Description**: The name that you specified for the Node.

## `node_interface_mappings`{% #node_interface_mappings %}

**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `NodeInterfaceMappings`**Description**: Documentation update needed

- `logical_interface_name`**Type**: `STRING`**Provider name**: `LogicalInterfaceName`**Description**: A uniform logical interface name to address in a MediaLive channel configuration.
- `network_interface_mode`**Type**: `STRING`**Provider name**: `NetworkInterfaceMode`
- `physical_interface_name`**Type**: `STRING`**Provider name**: `PhysicalInterfaceName`**Description**: The name of the physical interface on the hardware that will be running Elemental anywhere.

## `role`{% #role %}

**Type**: `STRING`**Provider name**: `Role`**Description**: The initial role current role of the Node in the Cluster. ACTIVE means the Node is available for encoding. BACKUP means the Node is a redundant Node and might get used if an ACTIVE Node fails.

## `sdi_source_mappings`{% #sdi_source_mappings %}

**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `SdiSourceMappings`**Description**: An array of SDI source mappings. Each mapping connects one logical SdiSource to the physical SDI card and port that the physical SDI source uses.

- `card_number`**Type**: `INT32`**Provider name**: `CardNumber`**Description**: A number that uniquely identifies the SDI card on the node hardware.
- `channel_number`**Type**: `INT32`**Provider name**: `ChannelNumber`**Description**: A number that uniquely identifies a port on the SDI card.
- `sdi_source`**Type**: `STRING`**Provider name**: `SdiSource`**Description**: The ID of the SdiSource to associate with this port on this card. You can use the ListSdiSources operation to discover all the IDs.

## `state`{% #state %}

**Type**: `STRING`**Provider name**: `State`**Description**: The current state of the Node.

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`