> ## Documentation Index
> Fetch the complete documentation index at: https://red5.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Create and Configure Red5 Cloud Node Groups

> Create Red5 Cloud deployments, configure ingress and egress for multiple regions, set up cloud storage, schedule runtimes, and manage existing deployments.

A deployment is your streaming environment — a named group of Red5 Pro nodes spread across one or more regions that work together to ingest and distribute live streams. You can run multiple deployments simultaneously: one for production, one for testing, one for a scheduled event, or any combination that fits your workflow.

## Deployments page

When you open the **Deployments** page in the Management Console you see a table of all your deployments with the following columns:

| Column                    | Description                                                                                   |
| ------------------------- | --------------------------------------------------------------------------------------------- |
| **Deployment Name**       | The name you gave the deployment. Also called the `nodeGroup` name in the Stream Manager API. |
| **Publishers**            | Number of publishers currently connected.                                                     |
| **Subscribers**           | Number of subscribers currently connected.                                                    |
| **State**                 | `Starting`, `Active`, or `Stopped`.                                                           |
| **Regions**               | The regions where the deployment runs.                                                        |
| **Start Date / End Date** | Scheduled start and end times, if applicable.                                                 |

<Note>
  The **Baseline** deployment is a system default that cannot be edited or deleted.
</Note>

## Add a new deployment

<Steps>
  <Step title="Open the Add New Deployment form">
    Click **Add New Deployment** at the top of the Deployments page.
  </Step>

  <Step title="Name your deployment">
    Enter a **Deployment Name** that describes its purpose (for example, `production-us` or `event-2026-q1`). This name is also used as the `nodeGroup` name when you make Stream Manager API calls.

    Optionally configure a **Round Trip Authentication** endpoint and a **Webhooks** endpoint if your application requires them.
  </Step>

  <Step title="Configure the default region">
    Click **Settings** next to your default region to open the region configuration panel.
  </Step>

  <Step title="Add additional regions (optional)">
    Click the **+** button to add another region, select it from the list, confirm, then click **Settings** next to the new region to configure it.
  </Step>

  <Step title="Configure storage (optional)">
    Select the **Storage** tab to set up cloud storage for stream recordings. See [Storage configuration](#storage-configuration) below.
  </Step>

  <Step title="Set the deployment schedule">
    Choose whether the deployment runs continuously or on a schedule. See [Deployment schedule](#deployment-schedule) below.
  </Step>

  <Step title="Review and deploy">
    Review your settings on the summary screen. Click **Back** to make changes or **Deploy** to start the deployment process. Initial provisioning can take up to 15 minutes.
  </Step>
</Steps>

## Region settings

### Ingress (publishers)

The ingress settings control how many Origin nodes are provisioned and what stream quality they are sized for.

| Setting            | Description                                                                                                               |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------- |
| **Min publishers** | The minimum number of concurrent publishers the region always supports. Nodes stay running even when no one is streaming. |
| **Max publishers** | The upper limit Stream Manager will scale to. Setting this too low can cause streams to fail at high load.                |
| **Resolution**     | The highest resolution stream that will be ingested (e.g., 1080p).                                                        |
| **Bitrate**        | The maximum ingest bitrate in kbps.                                                                                       |
| **FPS**            | The maximum frames per second of the ingest stream.                                                                       |

<Warning>
  Setting minimum or maximum values too low can cause streams to fail under load. Setting them too high increases costs unnecessarily. Match these values to your expected concurrent publisher count and stream quality.
</Warning>

### Egress (subscribers)

| Setting             | Description                                                    |
| ------------------- | -------------------------------------------------------------- |
| **Min subscribers** | The base number of Edge nodes that stay running at all times.  |
| **Max subscribers** | The maximum number of Edge nodes Stream Manager will scale to. |

### Preprocessing

Preprocessing normalizes incoming streams before they are distributed. Enable it when you cannot control encoder settings directly (for example, with third-party software that sends B-frames).

| Setting                  | Description                                                           |
| ------------------------ | --------------------------------------------------------------------- |
| **Enable preprocessing** | Toggle to activate stream normalization.                              |
| **Average bitrate**      | Target average bitrate for the normalized stream.                     |
| **Maximum bitrate**      | Peak bitrate cap. Typically set to the same value as average bitrate. |
| **MinQP**                | Minimum quantization parameter. A typical value is `12`.              |
| **MaxQP**                | Maximum quantization parameter. A typical value is `48`.              |

<Tip>
  If your stream appears to jump back and forth in time, B-frames are likely the cause. Enable preprocessing or configure your encoder to use the H.264 Baseline profile to eliminate them.
</Tip>

After configuring ingress, egress, and preprocessing, click **Save Region Configuration** to save the settings for that region.

## Storage configuration

To record published streams to cloud storage, select the **Storage** tab during deployment creation.

<Steps>
  <Step title="Select a storage vendor">
    Choose your cloud storage provider from the dropdown (for example, AWS S3).
  </Step>

  <Step title="Enter credentials">
    Provide your storage **Access Key** and **Secret**.
  </Step>

  <Step title="Set bucket details">
    Enter the **Bucket Name** and the **Region** where your bucket is located.
  </Step>

  <Step title="Test and continue">
    Click **Test** to verify the connection, then click **Next**.
  </Step>
</Steps>

## Deployment schedule

<Tabs>
  <Tab title="Always On">
    Toggle **Always On** to keep the deployment running continuously with no scheduled stop time. Use this for production environments that must be available at all times.
  </Tab>

  <Tab title="Scheduled">
    Enter a **Start Date**, **End Date**, **Start Time**, **End Time**, and **Time Zone** to automatically start and stop the deployment. Scheduled deployments are useful for live events with defined broadcast windows.
  </Tab>
</Tabs>

## Managing existing deployments

Each row in the Deployments table has a **context menu** (three-dot icon) with the following actions:

<AccordionGroup>
  <Accordion title="Pub/Sub Details">
    View the endpoints and embed code you need to start publishing and playing streams.

    | Item                         | Description                                                    |
    | ---------------------------- | -------------------------------------------------------------- |
    | **WHIP Publishing Endpoint** | Use this URL with a WebRTC (WHIP) encoder to publish a stream. |
    | **RTMP Publishing Endpoint** | Use this URL with an RTMP encoder such as OBS.                 |
    | **WHEP Playback Endpoint**   | Use this URL to play back the stream over WebRTC (WHEP).       |
    | **Embedded Player Code**     | Copy-paste HTML you can drop directly into your website.       |
  </Accordion>

  <Accordion title="Restart Deployment">
    Restarts all nodes in the deployment. You will be asked to confirm before the restart begins.
  </Accordion>

  <Accordion title="Edit Deployment">
    Returns you to the deployment configuration form where you can modify regional settings, storage, scheduling, and other options.
  </Accordion>

  <Accordion title="Delete Deployment">
    Permanently removes the deployment and all its nodes. You will be asked to confirm before deletion. This action cannot be undone.

    <Warning>
      The Baseline deployment cannot be deleted or edited.
    </Warning>
  </Accordion>
</AccordionGroup>