For JAR location, type or browse to the
location of your script. The value must be in the form
BucketName/path/ScriptName.

For Arguments, leave the field blank.

For Action on failure, accept the default
option (Continue).

Click Add. The step appears in the console with a
status of Pending.

The status of the step changes from Pending to Running to Completed as the
step runs. To update the status, click the Refresh icon
above the Actions column.

Launching a Cluster and Submitting a
Cascading Step Using the AWS CLI

This example describes how to use the AWS CLI to create a cluster and submit a Cascading
step. The Cascading SDK includes Cascading and Cascading-based tools such as
Multitool and Load. For more information, go to http://www.cascading.org/sdk/.

To create a cluster and submit a Cascading step using the AWS CLI

Type the following command to launch your cluster and submit a Cascading step. Replace
myKey with the name of your EC2 key pair and
replace mybucket with the name of your Amazon S3
bucket.

When you specify the instance count without using the
--instance-groups parameter, a single Master node is
launched, and the remaining instances are launched as core nodes. All nodes
will use the instance type specified in the command.

Note

If you have not previously created the default EMR service role
and EC2 instance profile, type aws emr
create-default-roles to create them before typing the
create-cluster subcommand.