Wrap a WSGI application in an AWS Lambda handler function for running on API Gateway or an ALB.
A quick example:
from apig_wsgi import make_lambda_handler
from myapp.wsgi import app
# Configure this as your entry point in AWS Lambda
lambda_handler = make_lambda_handler(app)Installation
Use pip:
python -m pip install apig-wsgiPython 3.5 to 3.8 supported.
Usage
make_lambda_handler(app, binary_support=False, non_binary_content_type_prefixes=None)
app should be a WSGI app, for example from Django’s wsgi.py or Flask’s Flask() object.
If you want to support sending binary responses, set binary_support to True. ALB’s support binary responses by default, but on API Gateway you need to make sure you have '*/*' in the ‘binary media types’ configuration on your Rest API. You will need to configure this through API Gateway directly, CloudFormation, SAM, or whatever tool your project is using. Whilst API Gateway supports a list of binary media types, using '*/*' is the best way to configure this, since it is used to match the request ‘Accept’ header as well, which WSGI applications are likely to ignore.
Note that binary responses aren’t sent if your response has a ‘Content-Type’ starting ‘text/’, ‘application/json’ or ‘application/vnd.api+json’ - this is to support sending larger text responses. To support other content types than the ones specified above, you can set non_binary_content_type_prefixes to a list of content type prefixes of your choice.
If the event from API Gateway contains the requestContext key, for example from custom request authorizers, this will be available in the WSGI environ at the key apig_wsgi.request_context.
If you want to inspect the full event from API Gateway, it’s available in the WSGI environ at the key apig_wsgi.full_event.
If you need the Lambda Context object, it’s available in the WSGI environ at the key apig_wsgi.context.
Multiple values for headers and query parameters are supported. They are enabled automatically on API Gateway but need explict activation on ALB’s.
Example
An example application with Ansible deployment is provided in the example/ directory in the repository. See the README.rst there for guidance.
1 maintainer
Metadata
1 maintainer
Release files for apig-wsgi 2.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| apig-wsgi-2.7.0.tar.gz | 46.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apig_wsgi-2.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 52.2 kB
Release files / apig-wsgi-2.7.0.tar.gz
| Download URL | apig-wsgi-2.7.0.tar.gz |
|---|---|
| Size | 46.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e155e91e21804434b11851017d5b6647a8fb8eb7f0476f5e9446979cc7f48af
|
|
BLAKE2b-256 checksum How to use checksums |
114d84268d3947202d46d906915152d311e005d7541e12b448877629320b05d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.3
|
Release files / apig_wsgi-2.7.0-py3-none-any.whl
| Download URL | apig_wsgi-2.7.0-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fe7be6513ddbeebf970670fd5df4cef8abcb99d5d546cdf605c532b8fce1a2da
|
|
BLAKE2b-256 checksum How to use checksums |
32b3377081d9a942b286a34ca534d452e0da1972bff1de6d0fe646812e7f0d6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.3
|
