Installing Driven Beta on an Amazon EMR Master Node
version 1.2Installing the Beta Plugin on EMR
If you run your applications in an Amazon Web Services Elastic MapReduce (AWS EMR) cluster, use a bootstrap action to install the plugin. The bootstrapping works with both persistent EMR clusters as well as auto-terminating clusters.
You can bootstrap by using either the AWS command-line interface (CLI) or the AWS Management Console. Bootstrapping installs the plugin on the EMR master node so that Cascading applications launched from the AWS CLI or the Management Console automatically operate with the plugin.
Amazon Web Services Command-Line Interface
The following code example shows you how to bootstrap Driven to an EMR cluster if you want to use the AWS CLI. Note the following about the code example:
-
The argument
"–api-key,${DRIVEN_API_KEY}"appears in the following code. Using a Driven API key is optional. Omit this argument if you do not want to enable team features in Driven. -
${DRIVEN_API_KEY}is a variable, which must be replaced with your real key if you want to pass the API key.
--bootstrap-actions Path=s3://files.concurrentinc.com/driven/1.2/driven-plugin/install-driven-plugin.sh,Args="–api-key,${DRIVEN_API_KEY}"
Amazon Web Services Management Console
To bootstrap the Driven Plugin using the AWS Management Console:
-
Navigate to the Create Cluster window.
-
Select the option to add a custom bootstrap action.
-
Enter the configuration for the new bootstrap action:
-
Name:
Driven Bootstrap Action -
S3 Location:
s3://files.concurrentinc.com/driven/1.2/driven-plugin/install-driven-plugin.sh -
Argument (Optional):
–api-key ${DRIVEN_API_KEY}} (This argument is required only if you want to enable the teams feature in Driven. Substitute${DRIVEN_API_KEY}with your value.)
-
Start Monitoring Your Data Applications
You are now ready to see how your applications are doing. See the Using Driven section of the Getting Started page.