Aws emr unable to install python library in bootstrap shell script

When working with AWS EMR, it is common to encounter issues with installing Python libraries in the bootstrap shell script. This can be frustrating, but there are several ways to solve this problem. In this article, we will explore three different solutions to this issue.

Solution 1: Using pip install in the bootstrap script

One way to solve this problem is by using the pip install command directly in the bootstrap shell script. This allows you to install the required Python libraries during the EMR cluster setup. Here is an example of how you can do this:


# Install Python libraries using pip
sudo pip install library_name

This solution is simple and straightforward. However, it may not work in all cases, especially if the required libraries have complex dependencies or require additional setup steps. In such cases, you may need to explore alternative solutions.

Solution 2: Using a bootstrap action script

Another approach is to use a bootstrap action script to install the Python libraries. This allows you to execute custom scripts during the EMR cluster setup. Here is an example of how you can do this:


# Create a custom bootstrap action script
echo '#!/bin/bash' >
echo 'sudo pip install library_name' >>

# Execute the bootstrap action script
sudo chmod +x

This solution provides more flexibility as you can include additional setup steps in the bootstrap action script. However, it requires creating and managing an additional script file.

Solution 3: Using a custom AMI

If the previous solutions do not work for your specific case, you can consider creating a custom Amazon Machine Image (AMI) with the required Python libraries pre-installed. This allows you to launch EMR clusters using the custom AMI, ensuring that the libraries are already available. Here is an example of how you can do this:

# Launch an EMR cluster using the custom AMI
aws emr create-cluster --name "My Cluster" --release-label emr-6.4.0 --applications Name=Hadoop Name=Spark --ec2-attributes KeyName=myKey --instance-type m5.xlarge --instance-count 3 --use-default-roles --custom-ami-id ami-1234567890abcdef0

This solution requires more initial setup as you need to create and manage a custom AMI. However, it provides the most control and ensures that the required Python libraries are always available.

After exploring these three solutions, it is clear that the best option depends on your specific requirements and constraints. If you have simple library dependencies, Solution 1 using pip install in the bootstrap script may be sufficient. If you need more flexibility and additional setup steps, Solution 2 using a bootstrap action script is a good choice. Finally, if you require complete control and want to ensure the availability of the libraries, Solution 3 using a custom AMI is the way to go.

Ultimately, the best option is the one that meets your specific needs and allows you to successfully install Python libraries in the bootstrap shell script of your AWS EMR cluster.

Rate this post

11 Responses

  1. I cant believe people are still struggling with this! Solution 2 FTW – bootstrap action script all the way! 💪

    1. Wow, calm down there buddy. Not everyone is a coding genius like you. Some of us are still learning and figuring things out. Maybe instead of boasting, you could offer some helpful advice to those who are struggling. Just a thought.

Leave a Reply

Your email address will not be published. Required fields are marked *

Table of Contents