Serverless Python Requirements
A Serverless v1.x plugin to automatically bundle dependencies from
requirements.txt and make them available in your
Requires Serverless >= v1.12
sls plugin install -n serverless-python-requirements
Compiling non-pure-Python modules or fetching their manylinux wheels is
supported on non-linux OSs via the use of Docker and the
To enable docker usage, add the following to your
The dockerizePip option supports a special case in addition to booleans of
'non-linux' which makes
it dockerize only on non-linux environments.
To utilize your own Docker container instead of the default, add the following to your
custom:pythonRequirements:dockerImage: <image name>:tag
This must be the full image name and tag to use, including the runtime specific tag if applicable.
Alternatively, you can define your Docker image in your own Dockerfile and add the following to your
Dockerfile the path to the Dockerfile that must be in the current folder (or a subfolder).
Please note the
dockerImage and the
dockerFile are mutually exclusive.
To install requirements from private git repositories, add the following to your
custom:pythonRequirements:dockerizePip: truedockerSsh: true
dockerSsh option will mount your
$HOME/.ssh/known_hosts as a
volume in the docker container. If your SSH key is password protected, you can use
$SSH_AUTH_SOCK is also mounted & the env var set.
It is important that the host of your private repositories has already been added in your
$HOME/.ssh/known_hosts file, as the install process will fail otherwise due to host authenticity
Pipenv support ✨🍰✨
If you include a
Pipfile and have
pipenv installed instead of a
requirements.txt this will use
pipenv lock -r to generate them. It is fully compatible with all options such as
dockerizePip. If you don't want this plugin to generate it for you, set the following option:
Dealing with Lambda's size limitations
To help deal with potentially large dependencies (for example:
scikit-learn) there is support for compressing the libraries. This does
require a minor change to your code to decompress them. To enable this add the
following to your
and add this to your handler module before any code that imports your deps:
try:import unzip_requirementsexcept ImportError:pass
Works on non 'win32' environments: Docker, WSL are included
To remove the tests, information and caches from the installed packages, enable the
slim option. This will:
.so files, remove
Custom Removal Patterns
To specify additional directories to remove from the installed packages,
define the patterns using regex as a
slimPatterns option in serverless config:
custom:pythonRequirements:slim: trueslimPatterns:- "*.egg-info*"
This will remove all folders within the installed requirements that match
the names in
You can omit a package from deployment with the
noDeploy option. Note that
dependencies of omitted packages must explicitly be omitted too.
By default, this will not install the AWS SDKs that are already installed on
Lambda. This example makes it instead omit pytest:
Extra Config Options
extra pip arguments
You can specify extra arguments to be passed to pip like this:
custom:pythonRequirements:dockerizePip: truepipCmdExtraArgs:- --cache-dir- .requirements-cache
--cache-dir don't forget to also exclude it from the package.
Customize requirements file name
pip workflows involve using requirements files not named
To support these, this plugin has the following option:
If you have different python functions, with different sets of requirements, you can avoid including all the unecessary dependencies of your functions by using the following structure:
├── serverless.yml ├── function1 │ ├── requirements.txt │ └── index.py └── function2 ├── requirements.txt └── index.py
With the content of your
package:individually: truefunctions:func1:handler: index.handlermodule: function1func2:handler: index.handlermodule: function2
The result is 2 zip archives, with only the requirements for function1 in the first one, and only the requirements for function2 in the second one.
Quick notes on the config file:
modulefield must be used to tell the plugin where to find the
requirements.txtfile for each function.
handlerfield must not be prefixed by the folder name (already known through
module) as the root of the zip artifact is already the path to your function.
Customize Python executable
Sometimes your Python executable isn't available on your
python3.6 (for example, windows or using pyenv).
To support this, this plugin has the following option:
Vendor library directory
For certain libraries, default packaging produces too large an installation,
even when zipping. In those cases it may be necessary to tailor make a version
of the module. In that case you can store them in a directory and use the
vendor option, and the plugin will copy them along with all the other
dependencies to install:
custom:pythonRequirements:vendor: ./vendored-librariesfunctions:hello:handler: hello.handlervendor: ./hello-vendor # The option is also available at the function level
requirements.zip(if using zip support) files are left
behind to speed things up on subsequent deploys. To clean them up, run
sls requirements clean. You can also create them (and
using zip support) manually with
sls requirements install.
Invalidate requirements caches on package
If you are using your own Python library, you have to cleanup
.requirements on any update. You can use the following option to cleanup
.requirements everytime you package.
custom: pythonRequirements: invalidateCaches: true
🍎🍺🐍 Mac Brew installed Python notes
Brew wilfully breaks the
--target option with no seeming intention to fix it
which causes issues since this uses that option. There are a few easy workarounds for this:
- Create a virtualenv and activate it while using serverless.
Also, brew seems to cause issues with pipenv, so make sure you install pipenv using pip.
For usage of
dockerizePip on Windows do Step 1 only if running serverless on windows, or do both Step 1 & 2 if running serverless inside WSL.
- Enabling shared volume in Windows Docker Taskbar settings
- Installing the Docker client on Windows Subsystem for Linux (Ubuntu)
Native Code Dependencies During Build
Some Python packages require extra OS dependencies to build successfully. To deal with this, replace the default image (
lambci/lambda:python3.6) with a
# AWS Lambda execution environment is based on Amazon Linux 1FROM amazonlinux:1# Install Python 3.6RUN yum -y install python36 python36-pip# Install your dependenciesRUN curl -s | python3RUN yum -y install python3-devel mysql-devel gcc# Set the same WORKDIR as default imageRUN mkdir /var/taskWORKDIR /var/task
Then update your
Native Code Dependencies During Runtime
Some Python packages require extra OS libraries (
*.so files) at runtime. You need to manually include these files in the root directory of your Serverless package. The simplest way to do this is to commit the files to your repository:
For instance, the
mysqlclient package requires
libmysqlclient.so.1020. If you use the Dockerfile from the previous section, you can extract this file from the builder Dockerfile:
- Extract the library:
docker run --rm -v "$(pwd):/var/task" sls-py-reqs-custom cp -v /usr/lib64/mysql57/libmysqlclient.so.1020 .
(If you get the error
Unable to find image 'sls-py-reqs-custom:latest' locally, run
sls package to build the image.)
2. Commit to your repo:
git add libmysqlclient.so.1020git commit -m "Add libmysqlclient.so.1020"
- Verify the library gets included in your package:
sls packagezipinfo .serverless/xxx.zip
(If you can't see the library, you might need to adjust your package include/exclude configuration in
- @dschep - Lead developer & maintainer
- @azurelogic - logging & documentation fixes
- @abetomo - style & linting
- @angstwad -
- @mather - the cache invalidation option
- @rmax - the extra pip args option
- @bsamuel-ui - Python 3 support
- @suxor42 - fixing permission issues with Docker on Linux
- @mbeltran213 - fixing docker linux -u option bug
- @Tethik - adding usePipenv option
- @miketheman - fixing bug with includes when using zip option
- @wattdave - fixing bug when using
- @heri16 - fixing Docker support in Windows
- @ryansb - package individually support
- @cgrimal - Private SSH Repo access in Docker,
dockerFileoption to build a custom docker image, real per-function requirements, and the
- @kichik - Imposed windows &
noDeploysupport, switched to adding files straight to zip instead of creating symlinks, and improved pip chache support when using docker.
- @dee-me-tree-or-love - the
- @alexjurkiewicz - docs about docker workflows