I am attempting to run a Python script to automate some tasks in my AWS environment, but I keep getting hit with the "ImportError: No module named boto3" message as soon as the execution starts. I thought the AWS SDK was included in Python by default, but it seems I am missing a installation step. I am working on a local machine with both Python 2.7 and Python 3.10 installed. How do I properly install the boto3 library so that my interpreter can find it, and should I be using a virtual environment to manage this dependency for my cloud projects?
3 answers
The error "ImportError: No module named boto3" simply means that the Python interpreter you are currently using does not have the AWS SDK for Python installed in its site-packages directory. To fix this, you need to use the Python package manager, pip. Open your terminal or command prompt and run pip install boto3. However, since you have multiple versions of Python installed, it is highly recommended to use python3 -m pip install boto3 to ensure it is mapped to your Python 3 environment. For professional cloud development, always use a virtual environment via python -m venv venv. This keeps your project dependencies isolated and prevents version conflicts between different AWS automation tools you might be building.
Are you seeing this error while running the script locally in your IDE, or are you getting this inside a specific environment like an AWS Lambda function or a Docker container?
You can verify the installation by running pip show boto3 in your terminal. If it doesn't show a version number and location, the installation didn't complete successfully.
I agree with Brenda. Checking the version is a great way to confirm. Also, once it is installed, make sure your script starts with import boto3 at the very top to properly initialize the SDK.
That is an excellent question, Ryan. If this is happening in AWS Lambda, it's actually quite strange because boto3 is typically included in the Lambda execution environment by default. However, if you are using a custom container or a specific runtime version, you might still need to package it as a Lambda Layer. For local development, the most common culprit is usually an IDE like VS Code or PyCharm pointing to the wrong Python interpreter that doesn't have the library installed yet. Always double-check which "python" your terminal is actually calling by using the which python or where python command.