Quick start

pip intall lambda-requests

>>> import lambda_requests
>>> lr = lambda_requests.Session()
>>> lr.get("http+lambda://flaskexp-test/test/foo")
<Response [200]>

[default]
aws_access_key_id =  XXXXXXXXXXXXXXXXXXXX
aws_secret_access_key = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

[profile default]
region = us-west-2

Why

In using REST microservice architecture it is important to be able to conveniently make calls from one service to another. To use this pattern in AWS serverless ecosphere along with Lambda one is practically forced to stand up an API Gateway in front of the lambda. This has several distinct disadvantages, all mostly along the lines of security.

• API Gateway publicly exposes endpoints

• API Gateway uses own authentication / authorization schema. While Lambda already supplies us with IAM.

• Extra dependencies in call chain. While availability is high, latency may still be of concern.

Over all, to reduce exposure of private sub-services, re-use IAM authentication / authorization and reduce latency.

How does its work

Simple, we register a new protocol name with requests and use a lambda specific transport adapter which translates a requests request to lambda invoke compatible with AWS API Gateway simple proxy format.

Limitations

Following functionality has not been tested and is likely to not be functional:

• Cookies

• Basicauth