Control-M for AWS Step Functions

AWS Step Functions enables you to create visual workflows that can integrate other AWS services.

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

• Execute AWS Step Function state machines (workflows), define state machine parameters, and add job logs to the output.

• Manage AWS Step Functions credentials in a secure connection profile.

• Connect to any AWS Step Functions endpoint.

• Introduce all Control-M capabilities to Control-M for AWS Step Functions, including advanced scheduling criteria, complex dependencies, resource pools, lock resources, and variables.

• Integrate AWS Step Functions jobs with other Control-M jobs into a single scheduling environment.

• Monitor the status, results, and output of AWS Step Functions jobs.

• Attach an SLA job to the AWS Step Functions jobs.

• Run 50 AWS Step Functions jobs simultaneously per Agent.

Setting up Control-M for AWS Step Functions

This procedure describes how to deploy the AWS Step Functions plug-in, create a connection profile, and define an AWS Step Functions job in Control-M SaaS 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 higher is installed.

1. On the Agent host, run one of the following commands to set the Java environment variable:

   • Linux:

     • Bourne shell/bash: export BMC_INST_JAVA_HOME=<java_directory>

     • csh/tcsh: setenv BMC_INST_JAVA_HOME <java_directory>

   • Windows: set BMC_INST_JAVA_HOME="<java_directory>"

2. Do one of the following:

   • Install: Run one of the following provision image commands:

     • Linux: ctm provision image ASF_plugin.Linux

     • Windows: ctm provision image ASF_plugin.Windows

   • Upgrade: Run the following command:

     ctm provision agent::update

3. Create an AWS Step Functions connection profile in Control-M SaaS or Automation API, as follows:

   • Control-M SaaS: Create a Centralized Connection Profile with AWS Step Functions Connection Profile Parameters

   • Automation API: ConnectionProfile:AWS Step Functions

4. Define an AWS Step Functions job in Control-M SaaS or Automation API, as follows:

   • Control-M SaaS: Create a Job with AWS Step Functions Job parameters

   • Automation API: Job:AWS Step Functions

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.05	Added AWS Assume IAM Role cross-account authentication Added HTTP Codes, Rerun Interval, and Attempt Reruns parameters to the connection profile to rerun an execution step with an HTTP code
1.0.03	Eliminated redundant validation on the Connection Profile to avoid interference in the job execution.
1.0.00	Initial version