Applications and credentials

Open Applications after selecting the environment. The page shows Instance Manager, Feed Manager, Flow Manager, and Deploy Manager as enabled or not enabled.

Enable an Application

1. Find the application card.
2. Select Enable.
3. Open Application Settings and complete the settings shown for that application.
4. Test the application before assigning it to operators.

The edit action changes application metadata. Deleting an application removes it from the environment and may remove access to its configuration, so confirm dependencies first.

Add a Credential

Prepare WMSPanel API access

Before adding a WMS Panel credential, allow API requests from both CLOUDflex backend outbound CIDR ranges:

74.220.48.0/24
74.220.56.0/24

1. In WMSPanel, open Control, then API setup and the Pull API tab.
2. Add each CIDR range shown above to the API whitelist.
3. Save the WMSPanel settings.

WMSPanel checks the source IP of each API request. CLOUDflex may send requests from any address in either range, so allowing only one address can cause intermittent failures.

Caution

Do not replace these ranges with the CLOUDflex website address or domain name. WMSPanel requires the backend’s outbound source ranges.

Add the credential to CLOUDflex

1. Under Credentials, select Add Credential.
2. Enter a descriptive name.
3. Select AWS or WMS Panel.
4. Enter the key ID and secret.
5. Select Add Credential.

Choose the credential type

• AWS authorizes CLOUDflex to perform the approved cloud operations for a self-hosted AWS environment.
• WMS Panel connects Flow Manager to WMSPanel, the management service used to configure Nimble Streamer. CLOUDflex uses the key ID and secret to manage the signal-processing configuration on a Nimble-based flow engine.

Note

A WMS Panel credential is required only when the environment uses a Nimble-based flow engine. It is not required for Instance Manager, Feed Manager, Deploy Manager, or flow engines that do not use Nimble and WMSPanel.

Credentials are scoped to the active environment. Studio does not display the secret again. Rotate credentials in the source system and Studio according to your organization’s security process, and delete credentials that are no longer used.