Control-M for AWS ECS

AWS Elastic Container Service (ECS) is a container management service that enables you to execute, stop, manage, and monitor containerized applications in a cluster.

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

  • Connect to any AWS ECS endpoint from a single computer with secure login, which eliminates the need to provide authentication.
  • Integrate AWS ECS jobs with other Control-M jobs into a single scheduling environment.
  • Execute AWS ECS jobs with a Fargate, EC2, or external infrastructure.
  • Monitor the status, results, and output of AWS ECS jobs in the Monitoring domain.
  • Attach an SLA job to your AWS ECS jobs.
  • Introduce all Control-M capabilities to Control-M for AWS ECS including advanced scheduling criteria, complex dependencies, Resource Pools, Lock Resources, and variables.
  • Run 50 AWS ECS jobs simultaneously per Agent.

Setting up Control-M for AWS ECS

This procedure describes how to install the AWS ECS plug-in, create a connection profile, and define an AWS ECS 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 AWS_ECS_plugin.Linux
      • Windows: ctm provision image AWS_ECS_plugin.Windows
    • For an upgrade, use the following command:
      ctm provision agent::update
  3. Create an AWS ECS connection profile in Helix Control-M or Automation API, as follows:
  4. Define an AWS ECS 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 ACS042023.

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

Comments