Fan Out Batch Jobs using AWS Step Functions

This sample application uses AWS Step Functions to fan-out AWS Batch Submit Job based on a randomly generated list of integers.

Once state machine is executed, a user can go to AWS Batch console's Workflow Orchestrations and see the state machine.

This sample application showcases visualization of Step Functions state machines in AWS Batch console.

AWS Lambda used in this application is powered by AWS Graviton2 processors. Learn more about how you can get up to 34% better price performance by running your AWS Lambda functions on AWS Graviton2 Processors

Deploy the sample application

WARNING: Cleanup resources once done working with sample app. This sample app provisions VPC, Subnets, Internet Gateway, route tables, & EC2 instances which can incur cost

To use the SAM CLI, you need the following tools:

• SAM CLI - Install the SAM CLI
• Node.js - Install Node.js 14, including the NPM package management tool.
• Docker - Install Docker community edition

To build and deploy your application for the first time, run the following in your shell:

sam build
sam deploy --guided

The first command will build the source of your application. The second command will package and deploy your application to AWS, with a series of prompts:

• Stack Name: The name of the stack to deploy to CloudFormation. This should be unique to your account and region, and a good starting point would be something matching your project name.
• AWS Region: The AWS region you want to deploy your app to.
• Confirm changes before deploy: If set to yes, any change sets will be shown to you before execution for manual review. If set to no, the AWS SAM CLI will automatically deploy application changes.
• Allow SAM CLI IAM role creation: Many AWS SAM templates, including this example, create AWS IAM roles required for the AWS Lambda function(s) included to access AWS services. By default, these are scoped down to minimum required permissions. To deploy an AWS CloudFormation stack which creates or modifies IAM roles, the CAPABILITY_IAM value for capabilities must be provided. If permission isn't provided through this prompt, to deploy this example you must explicitly pass --capabilities CAPABILITY_IAM to the sam deploy command.
• Save arguments to samconfig.toml: If set to yes, your choices will be saved to a configuration file inside the project, so that in the future you can just re-run sam deploy without parameters to deploy changes to your application.

You can find your State Machine ARN in the output values displayed after deployment.

Cleanup

To delete the sample application that you created, use the AWS CLI. Assuming you used your project name for the stack name, you can run the following:

sam delete

Resources

See the AWS SAM developer guide for an introduction to SAM specification, the SAM CLI, and serverless application concepts.

Next, you can use AWS Serverless Application Repository to deploy ready to use Apps that go beyond hello world samples and learn how authors developed their applications: AWS Serverless Application Repository main page

Security

See CONTRIBUTING for more information.

License

This library is licensed under the MIT-0 License. See the LICENSE file.