In this article:
- Find an AWS Windows instance
- Register the instance
- Install the Agent Installation Script manually
- Contacting Cloud Application Manager Support
This tutorial will show you how to import an existing Windows instance that was auto-discovered in your AWS provider using Cloud Application Manager.
For further information about instance registering using Cloud Application Manager, please visit Register an Existing Instance.
You can check the full process by watching the following video:
Users who want to register their Windows instances into Cloud Application Manager to enable lifecycle management on them.
- A Windows machine
- An active Cloud Application Manager account
- An existing AWS account with active instances
Find an AWS Windows instance
Within the Cloud Application Manager workspace, navigate to your AWS provider and run the sync function by clicking Sync.
The sync process will discover unregistered AWS instances and list them under the Unregistered Instances tab.
Register the instance
Under the Unregistered Instances tab or within the Instances page, click the instance you want to import and register.
Provide any details for the instance in the fields provided.
Click Register to register the instance.
If you didn't provide the Private Key, Windows Username and Password fields Cloud Application Manager returns an error message because the agent installation script that allows CenturyLink to register the instance is not yet executed on this instance.
Install the Agent Installation Script manually
Copy the agent installation script provided in the Activity tab in the log details.
Log-in to the instance residing in your AWS provider.
Execute the agent installation script.
Once the script is executed, the instance will be available in Cloud Application Manager.
You can now use lifecycle application management features on this instance in Cloud Application Manager.
Contacting Cloud Application Manager Support
For issues related to API calls, send the request body along with details related to the issue.
In the case of a box error, share the box in the workspace that your organization and Cloud Application Manager can access and attach the logs.
- Linux: SSH and locate the log at /var/log/elasticbox/elasticbox-agent.log
- Windows: RDP into the instance to locate the log at ProgramDataElasticBoxLogselasticbox-agent.log