.TH "makeflow_amazon_batch_setup" 1 "" "CCTools 7.1.2 FINAL" "Cooperative Computing Tools"

.SH NAME
.LP
\fBmakeflow_amazon_batch_setup\fP - set up Amazon services for running Makeflow

.SH SYNOPSIS
.LP
\FC\fBmakeflow_amazon_batch_setup <desired-num-cores> <min-num-cores> <max-num-cores> <config-file> \fP\FT

.SH DESCRIPTION
.LP

\fBmakeflow_ec2_setup\fP prepares Amazon services for running a Makeflow. It creates a virtual private cluster, subnets, key pairs, and other details, and writes these out to a configuration file given by the fourth argument. If the fourth argument is not provided, then it will be writen out to \FCmakeflow_amazon_batch.config\FT in the director this script is called.  The first argument is the desired number of cores for the environment. The second argument is the minimum number of cores acceptable for the environment. The third argument is the maximum number of cores that the environment should ever have at its disposal.

Once the configuration file is created, you may run \FCmakeflow\FT
with the \FC-T amazon-batch\FT option and give the name of the created
config file with \FC--amazon-batch-config\FT.

When complete, you can clean up the virtual cluster and related
items by running \FCmakeflow_amazon_batch_cleanup\FT

.SH PRE-RUN SETUP
.LP

Before using \FCmakeflow_amazon_batch_setup\FT, make sure that you install the AWS Command
Line Interface tools, have the \FCaws\FT command in your PATH,
and run \FCaws configure\FT to set up your secret keys and default region.

Next, ensure that the IAM associated with the secret keys passed to \FCaws configure\FT has the following policies attached to it:

*AmazonEC2FullAccess

*AmazonS3FullAccess

*AWSBatchServiceRole

*AWSBatchFullAccess

After ensuring that, the script requires that you have the following Roles enabled on your account:

*AWSBatchServiceRole -- This should have an arn which looks like \FCarn:aws:iam:ACCOUNT_ID_NUM:role/service-role/AWSBatchServiceRole\FT which has the policy AWSBatchServiceRole attached.

*ecsInstanceRole -- This should have an arn which looks like \FCarn:aws:iam:ACCOUNT_ID_NUM:role/ecsInstanceRole\FT which has the policy AmazonEC2ContainerServiceforEC2Role attached.

The easiest way to create these roles is to enter the Amazon Batch dashboard and create an environment via their wizard. In the "Serice role" and "Instance role" fields, have "Create new role" selected.

When these steps have been accomplished, then the script will run correctly and setup for you a batch environment for you to run your makeflow in. 


.SH OPTIONS
.LP
None.

.SH EXAMPLES
.LP

.fam C
.nf
.nh
.IP "" 8
makeflow_amazon_batch_setup 3 2 4 my.config
makeflow -T amazon-batch --amazon-batch-config=my.config --amazon-ami=USER_PROVIDED_ECS_IMAGE_ARN example.makeflow
makeflow_amazon_batch_cleanup my.config
.fi
.hy
.fam
.P

.SH COPYRIGHT
.LP

The Cooperative Computing Tools are Copyright (C) 2005-2019 The University of Notre Dame.  This software is distributed under the GNU General Public License.  See the file COPYING for details.

.SH SEE ALSO
.LP


.IP \(bu 4
\fBCooperative Computing Tools Documentation\fP
.IP \(bu 4
\fBMakeflow User Manual\fP
.IP \(bu 4
\fBmakeflow(1)\fP \fBmakeflow_monitor(1)\fP \fBmakeflow_analyze(1)\fP \fBmakeflow_viz(1)\fP \fBmakeflow_graph_log(1)\fP \fBstarch(1)\fP \fBmakeflow_ec2_setup(1)\fP \fBmakeflow_ec2_cleanup(1)\fP