---
title: Adding a Broadcaster Cluster - Managed
slug: zen-master/adding-a-broadcaster-cluster-managed
docTags: 
createdAt: 2024-12-27T16:04:23.488Z
---

When creating a ZEN Master managed Broadcaster cluster, you specify the AWS, Azure or GCP instance type that will be used for this cluster. Make sure to select an instance type that supports the type of processing that will be done on this cluster. ZEN Master supports both standard CPU instances as well as Nvidia GPU instances on AWS, Azure and GCP (including Tesla V100 and T4, which support both HEVC decoding and encoding).

In addition, ZEN Master supports 5G Contribution and Distribution using the AWS Wavelength Zone. Before launching a wavelength zone instance, opt into the wavelength zone service, by enabling the feature via your AWS console. Due to instant type and public IP differences, wavelength zone and non-wavelength zone subnets are not interchangeable, and clusters can only choose one. For more information, see - [https://docs.aws.amazon.com/wavelength/latest/developerguide/what-is-wavelength.html](https://docs.aws.amazon.com/wavelength/latest/developerguide/what-is-wavelength.html)

**To add a managed Broadcaster Cluster:**

:::::WorkflowBlock
:::WorkflowBlockItem
In the main navigation, click **Broadcasters**.
:::

:::WorkflowBlockItem
Click **+ Add**.
The **Create New Broadcaster Cluste**r screen is displayed.

![Create Managed Cluster](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/rAduFlw6L99gyvS3Q3R0S-20251030-171905.png)
:::

:::WorkflowBlockItem
In the **Info** section, in the **Name** field, type a logical name for the Zixi Cluster resource.
:::

:::WorkflowBlockItem
In the **Tags** field, select one or more of the predefined Tags from the drop-down menu.
Tags are used for access control. By selecting a Tag you are relating this Cluster to an Tag. Tags are associated with certain roles (through the Users & Roles screen), and roles, in turn, are associated with users and user groups. If you would like to create a new Tag, see [Creating a Tag](docId\:YpM9tw81ap6nq8sTKv4Rd) .
:::

::::WorkflowBlockItem
In the **Events Configuration Profile** field, select from the dropdown list the profile that you would like to apply to this cluster. By default, the Defaultprofile is applied.

:::hint{type="info"}
Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger.
:::
::::

:::WorkflowBlockItem
In the **DNS Prefix** field, enter a unique domain name for sending the streams to/from this cluster.
:::

:::WorkflowBlockItem
Select the **DTLS** checkbox if you would like to activate DTLS encryption and authentication. (This feature is only supported for Broadcasters running v12.2+.)
:::

:::WorkflowBlockItem
If you selected the **DTLS** checkbox then the **Ignore DTLS certificate when not supported** checkbox appears. Select this checkbox if you would like to enable resources using older versions of Zixi software (\<v12.2) that don't support verification of the ZEN DTLS certificate to connect to this cluster.
:::

::::WorkflowBlockItem
Select the **Log SCTE-35** checkbox if you would like to log SCTE-35 markers for streams on this cluster.

:::hint{type="info"}
- To log SCTE-35 markers, SCTE-35 needs to be enabled both on the Ingest Cluster and in the Source configuration.
- SCTE-35 logging is only available for v13.1.40262+ Broadcasters.
:::
::::

:::WorkflowBlockItem
Select the **RTMP Server** checkbox if you would like to receive RTMP push inputs.
:::

:::WorkflowBlockItem
If you want to configure an alternative path for disaster recovery, in the **Alternative Cluster (Disaster Recovery)** field, select the Cluster that will be used as the alternative path. For more details, see [Disaster Recovery (Alternative Path)](docId\:poo4ZS1-ZjRa1snDylqE0) .
:::

:::WorkflowBlockItem
In the **Configuration** section, in the **Management Type** field, for a managed cluster, select one of the *AWS*, *Azure* or *GCP* accounts configured in ZEN Master from the list shown under AWS, Azure or GCP in the drop-down menu. To create a new cloud service account see [Linking an AWS Account](docId\:erygXkCUfmmZ8BaKidJz4), [Linking an Azure Account](docId\:jSST1KXHRRRFCdyc1lENl)  or [Linking a Google GCP Account](docId\:JBuzi2tJvSpS3o_VzVXxH) .
The Configuration fields for the selected type of managed clusters are displayed.

![Configuration for Managed Cluster Type](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/fGoO0rbr_n5ANj_EyHF3r_image.png)
:::

:::WorkflowBlockItem
Fill in your cloud service account details as follows:

- For an **AWS** cluster –
  1. In the **Region** field, specify the AWS region.
  2. In the **Key Pair** field, select from the drop-down list one of the available Key Pairs to access the cluster. If no Key Pair is displayed, then go to your Amazon account to setup your Key Pair.
  3. In the **VPC** field, select from the drop-down list one of the available VPC (Virtual Private Cloud) networks to which the cluster will be connected.
  4. In the **Subnets** field, select from the drop-down list one or more of the subnets that are available in this VPC. AWS Wavelength subnets are indicated with "WAVES-BOS". For more information about Wavelength, see - [https://docs.aws.amazon.com/wavelength/latest/developerguide/what-is-wavelength.html](https://docs.aws.amazon.com/wavelength/latest/developerguide/what-is-wavelength.html)
  5. In the **Security Groups** field, select from the drop-down list one or more of the security groups associated with this VPC. If no Security Group is displayed then go to your Amazon Account to configure your security groups (for guidance in setting up your Security Groups see [Amazon Security Groups](https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#SecurityGroups:)).
  6. If you  want to **use only private IPs**, check that box.
  7. In the **Architecture** field, select **64-bit (Arm)**, or **64-bit (x86)**.
  8. In the **Instance Type** field, select from the drop-down list one of the available AWS instance types that will be used in this cluster.
  9. In the **Root Device Size** field, enter the capacity of the hard drive (in GiB).
- For an **Azure** cluster –
  1. In the **Region** field, select from the drop-down list the location of the account to be used for this cluster.
  2. In the **Virtual Network** field, select from the drop-down list a VN in your Azure account.
  3. In the **Subnet** field, select from the drop-down list a subnet that is available in the specified VN.
  4. In the **Network Security Group** field, select from the drop-down list a network security group for this cluster.
- For a **GCP** account –
  1. In the **Region&#x20;**&#x66;ield, select from the drop-down list the region of the GCP account.
  2. In the **Zones** field, select from the drop-down list one or more zones in the specified region.
  3. In the **Network** field, select from the drop-down list one or more of the subnets that are available in the specified region.
  4. In the **Machine Type** field, select from the drop-down list the type of machine to be used for the cluster. (**Note**: Both n1 and n2 machine types are supported.)
  5. In the **GPU Type** field, select from the drop-down list the type of GPU to be used for the cluster.
  6. In the **Root Device Size** field, specify the size of the root device in GiB.
:::

:::WorkflowBlockItem
In the **Activation Key** field, input the activation key for your Zixi Broadcaster license.
:::

:::WorkflowBlockItem
In the **API User** field, enter the username for accessing the Zixi Broadcaster via API.
:::

:::WorkflowBlockItem
In the **API Password** field, enter the password for accessing the Zixi Broadcaster via API
:::

::::WorkflowBlockItem
In the **Broadcaster Version** field, select from the drop-down list the desired Broadcaster version that you would like to run on your cloud service machines.

:::hint{type="info"}
- The Broadcaster versions available for your account can be viewed and modified on the Customer Portal.
- Make sure to select a Broadcaster version that supports the type of processing that will be done on this cluster.
:::
::::

::::WorkflowBlockItem
In the **Authorization Mode** field, select one of the following options:

- **ZEN Master** – ZEN Master automatically verifies the authorization for each ZEN entity (e.g. sources, channels and targets) that accesses the Broadcaster cluster. If you would like to allow access to inputs/outputs that are not configured in ZEN Master, then in the **Allow access…** section, select the **Push Inputs** and/or **Pull Outputs**
- **Global Password&#x20;**– Broadcasters are automatically configured to authorize all connections using a single global password. The global password will be used in the Source Password field when you configure a Source. In the **Password** field, enter the password OR click **Random&#x20;**&#x74;o generate a random password.
- **Free for All&#x20;**– Broadcasters will be automatically configured to allow all inputs/outputs to connect. Select **Inputs** and/or **Outputs** to automatically allow them to connect.
- **Manual** – ZEN will not authorize connections. You will need to authorize each connection independently.

:::hint{type="info"}
All authorization modes other than *Manual* will override the authorization configured on your Broadcasters. Therefore, if you have streams on your Broadcasters that are not configured on ZEN Master, then any mode other than *Manual* or *Free for All* may interrupt those streams.
:::
::::

:::WorkflowBlockItem
If you want to **allow access to inputs not configured in ZEN Master**, check the types you want to allow, and check **Delete Protection** if you do not want to allow these inputs to be deleted via ZEN Master.
:::

:::WorkflowBlockItem
If you want to enable [Enabling the High-Performance Networking Feature (DPDK)](docId:37137sC8yzi5y_tose9_B), check th&#x65;**&#x20;DPDK Support** checkbox.
:::

:::WorkflowBlockItem
If you would like to adjust the advanced settings, click **Advanced**.
The **Advanced settings** are displayed:

![Advanced Settings](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/Rq3OdjP7gJU14oz6b4k2f_image.png)
:::

:::WorkflowBlockItem
You can adjust the following settings:

1. **Balance Pull Targets**– select one of the following load balancing methods for Pull outputs:
   - **Minimize the number of broadcasters&#x20;**(default)– transfers excess load to other broadcasters only when the allotted capacity on the host broadcaster is filled.
   - **Uniform distribution** – distributes the load equally between all available broadcasters under all circumstances.
2. **HTTP Streaming Port&#x20;**– You can change the HTTP streaming port from the default (*7777*) to a custom port. The custom port should match the configuration on the Zixi Broadcaster.
3. **Elastic IP Allocation IDs&#x20;**– Enter comma separated Elastic IP Allocation IDs. Elastic IPs are a set of fixed IPs provided by AWS, so that when ZEN Master launches an instance it will assign this instance with one one of these "known" elastic IP addresses. This known IP address can be configured in the Firewall security solution.&#x20;
4. **Require Elastic IP -&#x20;**&#x73;elect this checkbox to prevent ZEN Master from launching an instance if there are no more available Elastic IPs.&#x20;
5. **Bandwidth Limits**– set the bandwidth limits. Choose one of the two fields: **Input** - **Output**.
6. **Default HLS Segment Configuration -&#x20;**
7. **HLS/CMAF(DASH+fMP4 HLS) segment configuration&#x20;**– configure the *Count* and *Duration&#x20;*&#x70;arameters for HLS and DASH segments on this Broadcaster Cluster.
8. The **Transcode Thresholds** are used by ZEN Master to determine whether an additional transcoded Channel can be added to the broadcaster. The following thresholds can be adjusted:
   - **CPU Threshold&#x20;**– percentage of CPU being used.
   - **Memory Threshold&#x20;**– percentage of memory being used.
   - **GPU Threshold&#x20;**– percentage of GPU being used.[\[1\]](docId:6sLx4TD__ZKr2XFhO8qZ6)&#x20;
   - **GPU Memory Threshold&#x20;**– percentage of GPU memory being used.
   - **GPU Decoder Threshold&#x20;**– percentage of GPU decoder pipeline being used.
   - **GPU Encoder Threshold&#x20;**– percentage of GPU encoder pipeline being used.
9. **Enable Real-time Broadcaster process priority&#x20;**- this setting is deselected by default. You can increase the Broadcaster's process priority by selecting it. This may be beneficial for sending streams to highly sensitive IRDs. However, this should not be done without consulting with your customer success agent. ZEN Master will expect a response form the external server, consisting of a JSON object. The following details need to be configured:
   - Server endpoint - an external authorization URL for the server endpoint.&#x20;
   - Optional authorization header schema and credentials to access the service.
10. **External Authorization** - ZEN Master can, in addition to its standard internal authorization process, redirect the authorization of connections to an external service. For example, an external pay-per-view application, which confirms that a requesting end-device belongs to an account that has paid for a live event.&#x20;
    - Server endpoint - an external authorization URL for the server endpoint.
    - Optional Authorization header schema and credentials.
11. If you would like to track usage for this Broadcaster, enter your **Billing Code** details, see [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ) . (Supported for Broadcasters v14.8+)
12. If you would like to install AgentZ automatically, select the **Install AgentZ automatically** checkbox. Agent Z is a Sidecar tool that sits on a Zixi Broadcaster, it acquires the system health data and other statistics locally and pushes it to ZEN Master. By enabling this option, ZEN Master will automatically install AgentZ on any existing and future Broadcasters connected to the Cluster. The feature is off by default. Due to AgentZ installation requiring a restart, ZEN Master will not auto-install AgentZ on a Broadcaster that already contains any inputs to avoid disturbing active streams.
13. For **AWS** managed clusters, check the **Advanced Monitoring** box for Detailed CloudWatch Monitoring.
:::

:::WorkflowBlockItem
Click **Save**.
The new Broadcaster cluster is created in the system and added to the list of Broadcaster clusters. The status should change from *Pending* to *OK* after a few minutes.
:::
:::::

### Notes

1. The GPU thresholds are only relevant for transcoding workflows using Intel Quick Sync or NVIDIA GPUs.