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

# aws_medialive_cluster{% #aws_medialive_cluster %}

## `account_id`{% #account_id %}

**Type**: `STRING`

## `arn`{% #arn %}

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

## `channel_ids`{% #channel_ids %}

**Type**: `UNORDERED_LIST_STRING`**Provider name**: `ChannelIds`**Description**: An array of the IDs of the Channels that are associated with this Cluster. One Channel is associated with the Cluster as follows: A Channel belongs to a ChannelPlacementGroup. A ChannelPlacementGroup is attached to a Node. A Node belongs to a Cluster.

## `cluster_type`{% #cluster_type %}

**Type**: `STRING`**Provider name**: `ClusterType`**Description**: The hardware type for the Cluster.

## `id`{% #id %}

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

## `instance_role_arn`{% #instance_role_arn %}

**Type**: `STRING`**Provider name**: `InstanceRoleArn`**Description**: The ARN of the IAM role for the Node in this Cluster. Any Nodes that are associated with this Cluster assume this role. The role gives permissions to the operations that you expect these Node to perform.

## `name`{% #name %}

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

## `network_settings`{% #network_settings %}

**Type**: `STRUCT`**Provider name**: `NetworkSettings`**Description**: Network settings that connect the Nodes in the Cluster to one or more of the Networks that the Cluster is associated with.

- `default_route`**Type**: `STRING`**Provider name**: `DefaultRoute`**Description**: The network interface that is the default route for traffic to and from the node. MediaLive Anywhere uses this default when the destination for the traffic isn't covered by the route table for any of the networks. Specify the value of the appropriate logicalInterfaceName parameter that you create in the interfaceMappings.
- `interface_mappings`**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `InterfaceMappings`**Description**: An array of interfaceMapping objects for this Cluster. Each mapping logically connects one interface on the nodes with one Network. You need only one mapping for each interface because all the Nodes share the mapping.
  - `logical_interface_name`**Type**: `STRING`**Provider name**: `LogicalInterfaceName`**Description**: The logical name for one interface (on every Node) that handles a specific type of traffic. We recommend that the name hints at the physical interface it applies to. For example, it could refer to the traffic that the physical interface handles. For example, my-Inputs-Interface.
  - `network_id`**Type**: `STRING`**Provider name**: `NetworkId`**Description**: The ID of the network that you want to connect to the specified logicalInterfaceName.

## `state`{% #state %}

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

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`