Knowledge Base  /  Cloud Application Manager  /  Deploying Anywhere
Knowledge Base  /  Cloud Application Manager  /  Deploying Anywhere

Using Compute Instances

Updated by Sharon Wang on Nov 05, 2019
Article Code: kb/1271

In this article:


This article is meant to assist users of Cloud Application Manager trying to register their stand-alone/physical machines to CAM. You can bring your own infrastructure to Cloud Application Manager by installing the Cloud Application Manager agent and register it to Compute Instances Provider. This will enable lifecycle of the instance through Cloud Application Manager like with any other natively-deployed instance.


All users of Cloud Application Manager who wants to register their stand-alone machines to Compute Instances Provider.


  • An active Cloud Application Manager account
  • Any infrastructure capable of running Cloud Application Manager Agent.

Create a new Compute Instances Provider

To create a new provider, select Compute Instances from the Provider list and give it a name, then click on Save

New compute instances provider

Note: Unlike other provider types, this one does not require any synchronization process and it does not support deployment policies either, since there is no direct deployment support on it.

Register a Server into the Compute Instances provider

You can launch boxes on any infrastructure by running the Cloud Application Manager agent. The agent is required to execute scripts, manage box variables and run lifecycle operations. Once the provider is created, users can register VMs or physical machines to this Provider by using the code snippet provided by clicking Self-Register Scripts

Self-Register Scripts button

There are 2 scripts for Windows and Linux OS. In this article, we use Windows server as an example:

Self-Register Scripts

Note: If the proxy is specified, the snippet with be updated dynamically with its values to allow the machine to contact back to Cloud Application Manager through it.

Copy the script and run on the Windows server we have on CLC to trigger the self-register process:

Windows PowerShell script

The provider activity log will show an activity when an instance is asking to be registered in the provider. Once the script is completed, you can see the server registered:

The new instance registered in CAM

If you click on the instance, the instance details page will be displayed:

The new instance registered details

To learn more about Cloud application manager Self Register Instances, please review the Self Register Instances article.

Contacting Cloud Application Manager Support

We’re sorry you’re having an issue in Cloud Application Manager. Please review the troubleshooting tips, or contact Cloud Application Manager support with details and screenshots where possible.

For issues related to API calls, send the request body along with details related to the issue.

In the case of an error registering an instance, share the instance to a workspace that your organization and Cloud Application Manager support group can access and attach the logs.

  • Linux: SSH into the instance and locate the log at /var/log/elasticbox/elasticbox-agent.log
  • Windows: RDP into the instance to locate the log at \ProgramData\ElasticBox\Logs\elasticbox-agent.log
    If you have additional questions, please contact Cloud Application Manager Support