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:

• Execute AWS ECS jobs with a Fargate, EC2, or external infrastructure.
• Manage AWS ECS credentials in a secure connection profile.
• Connect to any AWS ECS endpoint.
• Integrate AWS ECS jobs with other Control-M jobs into a single scheduling environment.
• 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.

Control-M for AWS ECS Compatibility

The following table lists the prerequisites that are required to use the AWS ECS plug-in, each with its minimum required version.

Component	Version
Control-M/EM	9.0.21.100
Control-M/Agent	9.0.21.100
Control-M Application Integrator	9.0.21.100
Control-M Automation API	9.0.20.250

Control-M for AWS ECS is supported on Control-M Web and Control-M Automation API, but not on Control-M client.

To download the required installation files for each prerequisite, see Obtaining-Control-M-Installation-Files.

Setting up Control-M for AWS ECS

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

Before You Begin

Verify that Automation API is installed, as described in Automation API Installation.

Begin

1. Create a temporary directory to save the downloaded files.
2. Download the AWS ECS plug-in from the Control-M for AWS ECS download page in the EPD site.
3. Install the AWS ECS plug-in via one of the following methods:
   • (9.0.21 or higher) Use the Automation API Provision service:
     1. Log in to the Control-M/EM Server machine as an Administrator and store the downloaded zip file in the one of the following locations (within several minutes, the job type appears in Control-M Web):
        • Linux: $HOME/ctm_em/AUTO_DEPLOY
        • Windows: <EM_HOME>\AUTO_DEPLOY
     2. Log in to the Control-M/Agent machine and run the provision image command, as follows:
        • Linux: ctm provision image AWS_ECS_plugin.Linux
        • Windows: ctm provision image AWS_ECS_plugin.Windows
   • (9.0.20.200 or lower) Use the Automation API Deploy service, as described in deploy jobtype. 
4. Create an AWS ECS connection profile in Control-M Web or Automation API, as follows:
   • Web: Creating a Centralized Connection Profile with AWS ECS Connection Profile Parameters 
   • Automation API: ConnectionProfile:AWS ECS
5. Define an AWS ECS job in Control-M Web or Automation API, as follows:
   • Web: Creating a Job with AWS ECS Job parameters
   • Automation API: Job:AWS ECS

Change Log

The following table provides details about changes that were introduced in new versions of this plug-in:

Plug-in Version	Details
1.0.04	AWS patch applied, to resolve issue of bad URLs in the connection profile. Resolved issue of missing internal quotations in the API calls. Added ability to run multiple ECS jobs and get correct logs from CloudWatch.
1.0.05	Overrides are now optional. Get logs is now optional. Status Polling default value changed to 60.
1.0.06	Minor parameter changes.