A collection of AWS Lambda Layers for Python3.7 & Python3.8
List of all layer version arns are available by region here:
There might be multiple versions for a single package, this is because we publish a new layer version for every new version of the package or if the package dependencies (requirements.txt) has been updated. Refer to Layer expiry for more data.
For the full list of packages available click here, here are just some examples of the 60+ packages we build every week:
- aws-lambda-powertools
- aws-xray-sdk
- bcrypt
- beautifulsoup4
- boto3
- dynamodb-encryption-sdk
- idna
- lambda-cache
- nltk
- numpy
- opencv-python-headless
- openpyxl
- pandas
- parliament
- Pillow
- pulp
- pycryptodome
- PyJWT
- PyMUPDF
- pyqldb
- pytesseract
- pytz
- PyYAML
- requests
- slackclient
- spacy
Click on badge above to see the specific package version of the latest builds.
Layers are built with the latest package version (available on PyPI) every Monday 2am UTC.
You can either set one of the ARNs below as a layer in your function. Or download the layer and deploy a copy into your account.
Click links below for your preferred version of python, and then select your region of choice, you will see a full list of layer version ARNs to use.
Use the Get Layer Version by ARN in python or bash command which will provide an S3 location to download the layer as a zip.
Note: You can only get layers from the specific region your awscli is configured for, otherwise you'll get a AccessDeniedException error.
Some layer versions will have a time_to_live field. This is the date for when the layers will be deleted.
In general, layers are scheduled for deletion 30 days after a new layer version has been published for that package. If you use that latest version of a layer, you're guaranteed at least 30 days before the layer is deleted.
All functions deployed with a layer will still work indefinitely, but you won't be able to deploy new functions referencing a deleted layer version.
Special hand-crafted binaries for layers. These layers are not automatically built, and hence slower update cycles, and will only work with python3.7 functions as the underlying OS is Amazon Linux 1.
| Package | ARN | Version |
|---|---|---|
| tesseract | arn:aws:lambda:<region>:113088814899:layer:Klayers-python37-tesseract:1 | 4.1.0-rc11 |
| pip | arn:aws:lambda:<region>:113088814899:layer:Klayers-python37-pip:2 | 19.2.12 |
| netcat | arn:aws:lambda:<region>:113088814899:layer:Klayers-python37-netcat:2 | 0.7.13 |
| en_core_web_sm | arn:aws:lambda:<region>:770693421928:layer:Klayers-python38-spacy_model_en_small:1 | 2.2.54 |
1 Includes leptonica-1.76.0, libjpeg 6b (libjpeg-turbo 1.2.90) : libpng 1.2.49 : libtiff 4.0.3 : zlib 1.2.8 : libwebp 0.3.0
2 Python3.8 layers already have new version of pip, use only if on Python3.7
3 netcat-traditional with the -e option -- compiled for 64-bit to run on AWS Lambda
4 Spacy en_core_web_sm model, for use with the spacy layer refer here for more info.
No self-respecting architect would have a repo like this without a diagram -- so here it is:
- Chahna107 for adding tesseract config files into the tesseract layer.
- ~ Dependencies scanned by PyUp.io ~