Your first production
This is the shortest path to a successful CLOUDflex production. It covers the handoff between an administrator who prepares the environment and an operator who runs the machine.
Outcome
Section titled “Outcome”You will create or select an environment, deploy a production machine, connect to it, verify the production path, and stop billable resources when the test is complete.
Before You Begin
Section titled “Before You Begin”- An organization owner or administrator must be available for environment and permission setup.
- For a self-hosted environment, complete the AWS Self-Hosted Prerequisites.
- Know which AWS region and production application you intend to use.
- Prepare the operator’s computer and network for an Amazon DCV remote desktop session. NICE DCV was renamed Amazon DCV; CLOUDflex may still use the NICE DCV label in the interface.
Prepare the operator workstation
Section titled “Prepare the operator workstation”For normal show operation, use the native Amazon DCV client. It supports Windows, macOS, and Linux and provides the best fit for multi-monitor operation.
- Review the official Amazon DCV client requirements for the operator’s operating system.
- Open the Amazon DCV downloads page.
- Download the client for the operator’s computer. Do not download the server package.
- Install and open the client. Windows operators may use either the installable or portable client.
- Confirm the operator’s network can reach the production machine on the DCV port. Amazon DCV uses TCP port
8443by default, although an administrator may configure a different port.
The operator’s experience depends on screen activity, frame rate, image complexity, latency, packet loss, and enabled DCV quality options. Amazon DCV adapts its stream and does not specify a fixed bandwidth requirement. For production planning, reserve approximately:
| Operator display | Recommended available download bandwidth |
|---|---|
| One 1920 × 1080 monitor | 15–25 Mbps per operator |
| Two 1920 × 1080 monitors | 30–50 Mbps per operator |
These figures are planning allowances, not guaranteed minimums. Moving video, multiviewers, high frame rates, and high color accuracy can use more bandwidth. Use a wired connection where practical, avoid shared or congested Wi-Fi, and test from the operator’s real location before show day. Leave additional capacity for return video, communications, and other production traffic.
1. Create or Join the Organization
Section titled “1. Create or Join the Organization”Create your account or accept the invitation sent by your administrator. Confirm the correct organization appears in the organization switcher.
2. Create the Environment
Section titled “2. Create the Environment”An administrator creates a managed or self-hosted AWS environment and selects its region. After creation, select it in the environment switcher before continuing.
3. Enable the Required Applications
Section titled “3. Enable the Required Applications”An administrator enables the applications required for the test. A basic production normally needs Instance Manager. Enable Deploy Manager when the machine will be created from an approved template, Flow Manager for signal routing, and Feed Manager for browser monitoring.
Configure applications and credentials
4. Deploy a Production Machine
Section titled “4. Deploy a Production Machine”In Deploy Manager, choose an approved template, enter a stack name, review its defaults, and launch it. Wait for the deployment to finish before trying to operate the machine.
5. Give the Operator Access
Section titled “5. Give the Operator Access”Invite the operator as an organization member. Add environment permission for Instance Manager and the relevant studio. Allow enough time for setup, rehearsal, and recovery—not only the scheduled on-air window.
6. Start and Connect With Amazon DCV
Section titled “6. Start and Connect With Amazon DCV”- Open Instance Manager and confirm the correct environment and machine.
- Start the production machine.
- Wait for the machine to report
running. A newly started machine can require additional time before its DCV session accepts connections. - Choose NICE DCV as the connection type and select the connect control for the machine.
- Allow the browser to open the installed Amazon DCV client. If prompted, confirm the connection details supplied by CLOUDflex.
- Confirm that the remote desktop fits the intended monitor layout. The native client can extend full screen across multiple monitors when the server configuration supports it.
Use Web Interface when installing the native client is not practical. The browser client is useful for quick access, but the native client is recommended for regular multi-monitor production work.
7. Verify the Production
Section titled “7. Verify the Production”- Confirm the expected production application opens on the machine.
- Confirm required inputs are present.
- Confirm program video and audio reach the intended output or monitoring feed.
- Test the same connection path and viewer network that the crew will use on show day.
For routed signals, continue with Configure signal flows. For browser monitoring, continue with Configure monitoring feeds.
8. Shut Down Safely
Section titled “8. Shut Down Safely”- Stop contribution and output paths that should not remain active.
- Close the remote session.
- Stop the production machine in Instance Manager.
- Wait for it to report
stopped. - Check the Dashboard for other running machines.
- Ask an administrator to review Usage after records update.
Verify
Section titled “Verify”The first test is complete when the operator can connect, the signal path has been checked end to end, and every cloud resource that should stop reports a stopped state.