Control-M for AWS EC2

AWS Elastic Compute Cloud (EC2) enables you to create virtual machines in the Amazon cloud-computing platform.

Control-M for AWS EC2 enables you to do the following:

  • Connect to any AWS EC2 endpoint from a single computer with secure login, which eliminates the need to provide authentication.
  • Integrate AWS EC2 jobs with other Control-M jobs into a single scheduling environment.
  • Execute any of the following AWS EC2 job operations:
    • Create a virtual machine.
    • Create a virtual machine from a template.
    • Start an existing virtual machine.
    • Stop a running virtual machine.
    • Reboot a virtual machine.
    • Delete an existing virtual machine.
  • Monitor the status, results, and output of AWS EC2 jobs in the Monitoring domain.
  • Attach an SLA job to your AWS EC2 jobs.
  • Introduce all Control-M capabilities to Control-M for AWS EC2 including advanced scheduling criteria, complex dependencies, Resource Pools, Lock Resources, and variables.
  • Run 50 AWS EC2 jobs simultaneously per Agent.

Setting up Control-M for AWS EC2

This procedure describes how to install the AWS EC2 plug-in, create a connection profile, and define an AWS EC2 job in Helix Control-M and Automation API.

Before you Begin

  • Verify that Automation API is installed, as described in Setting up the API.
  • Verify that Agent version 9.0.21.080 or later is installed.

Begin

  1. On the Agent host, set the Java environment variable by running one of the following commands through a command line:
    • Linux:
      • Bourne shell/bash: export BMC_INST_JAVA_HOME=<java_11_directory>
      • csh/tcsh: setenv BMC_INST_JAVA_HOME <java_11_directory>
    • Windows: set BMC_INST_JAVA_HOME="<java_11_directory>"
  2. Run one of the following API commands:
    • For a fresh installation, use the provision image command:
      • Linux: ctm provision image AEC_plugin.Linux
      • Windows: ctm provision image AEC_plugin.Windows
    • For an upgrade, use the following command:
      ctm provision agent::update
  3. Create an AWS EC2 connection profile in Helix Control-M or Automation API, as follows:
  4. Define an AWS EC2 job in Helix Control-M or Automation API, as follows:

Note

To remove this plug-in from an Agent, follow the instructions in Removing a Plug-in. The plug-in ID is AEC082022.

Was this page helpful? Yes No Submitting... Thank you

Comments