Build a production

Build-time work establishes the environment, machines, signal paths, monitoring, access, and recovery plan before the crew goes on air.

Outcome

A production is ready to hand to operators when its infrastructure is deployed, access is assigned, signals have been tested end to end, and the shutdown plan is understood.

Before You Begin

• Identify the production applications and machine sizes required.
• Decide whether CLOUDflex or your organization manages the cloud account.
• Confirm the AWS region, network path, contribution protocol, outputs, and monitoring requirements.
• Assign an administrator who can manage environments and access.

Build Sequence

1. Create an environment for the correct cloud account and region.
2. Configure applications and credentials.
3. Create studios to group resources by show, client, or control room.
4. Deploy production machines from approved templates.
5. Use Instance Manager to assign machines to the correct studio, confirm their size and storage, and test remote access.
6. Configure signal flows for contribution, internal routing, and delivery.
7. Configure monitoring feeds for the people who need browser viewing.
8. Assign operator permissions with a practical access window.
9. Test startup, remote access, signals, monitoring, and shutdown.

Note

The current staged interface launches approved deployment templates. Saving a completed production as a new reusable template is not established in the current UI.

Verify

• Each machine reaches its expected state and accepts a remote connection.
• Every required input and output carries the expected picture and audio.
• Operators see only the applications and studios they need.
• A responsible person knows how to stop resources and verify shutdown.

What’s Next

Use the show-day workflow for rehearsal and production.