Skip to content
VSE Control-M Docs Site

AWS Lambda (via AWS Job)

AWS Lambda (via AWS Job)

Introduction

Maintainer: DBA Demo Admins DBA_Demo_Admins@bmc.com

AWS Lambda is a compute service that lets you run code without provisioning or managing servers.

Use Case Overview

This workflow allows organizations to automate the triggering of serverless functions alongside traditional workflows, enabling hybrid cloud and on-premise automation. Control-M provides centralized control for scheduling, monitoring, and managing dependencies for Lambda functions, ensuring they are executed based on events or schedules. This integration offers real-time visibility, error handling, and auditability for serverless processes, improving operational efficiency and governance.

Use Case Technical Explanation

This workflow will start by orchestrating AWS to create a compute environment first-job-run-environment using EC2 as the provisioning model. A job queue first-run-job-queue is defined. Depending on the run (1 or 2), job definitions for the first-run-batch job will change. On run 1, the first-run-batch job performs an “echo hello world” command, whereas on run 2, the first-run-batch job performs an “echo Howdy, world” command.

For additional information on the Helix Control-M AWS Job (Lambda) type, select the following link:

Demo Environment Information

EnvironmentStatusFolder Name
Helix ProductionAvailablezzz-aws-lambda-demo
VSE CTM PRODAvailablezzz-aws-lambda-demo
VSE CTM QAAvailablezzz-aws-lambda-demo