An on-demand, browser-compatible, proxy backed by AWS Lambda for anonymous browsing and web crawling. For normal web browsing, Proxy-On-Demand (POD) costs fractions of cents to operate and is price competitive with tiny EC2 instances, fitting entirely in the free-tier. For heavy loads, POD provides scalability in real-time, streaming up to 4K videos on youtube.

POD runs as a server on your local machine. When configured with POD (localhost:1080) as its proxy, your browser sends HTTP requests to POD and POD performs these requests on a Lambda function. For HTTPS traffic, POD requires a root CA certificate to be installed in the browser's certificate store. The local server decrypts the traffic locally and reissues the HTTPS requests, verifying the target server's identity in the process.

When a server returns a response that is too large to return directly in a Lambda response body, POD stores the response in S3 temporarily, before deleting it.

All traffic to AWS lambda is encrypted in flight with TLS. POD can also encrypt requests and metadata to make it visible only to the Lambda. The local server sends a session key, encrypted with the Lambda's public key, for each request. This key is used to encrypt both the request and the response, including any data that is placed in S3. For security purposes, the Lambda's private key can be encrypted with the Amazon KMS, otherwise it is stored in the Lambda's environment.

• A web browser (tested with Firefox)
• OpenSSL installed (to generate root CA certs)
• AWS credentials setup with aws configure

1. Install the dependencies in requirements.txt.
2. Create an IAM role for lambda (requires S3, SQS).
3. Run collect.sh from inside ./lambda and then ./deploy.sh.
4. Execute main.py -f <function_name>.
5. For best results, install an adblocker, setup a S3 bucket for large payload transfers, enable MITM, and run with the command ./main.py -m -f <function_name> -s3 <bucket_name>.
6. Set the browser's proxy configuration (by default: localhost:1080)

The daemon acts as a Man-in-the-Middle, generating certificates on the fly for requests. When proxying requests, the daemon will handle certificate validation in place of the browser.

• To use the MITM (HTTPS) proxy, run gen_cert.sh to generate a root CA certificate.
• Install this into your least favorite (non-banking) browser.
• Execute main.py -m.

All requests are proxied locally for debugging purposes.

• Execute main.py -l.

By default, data to the lambda is encrypted with TLS. However, this means that all parts of the AWS stack that the data traverses can see in plaintext request and response headers and bodies. This option allows encryption of request and response data so that only the daemon on localhost and the lambda (or an attacker with access to the lambda's environment variables) can decrypt it.

• Execute gen_rsa_kp.py.
• Set the private key as RSA_PRIVATE_KEY in the lambda's env
• Run main.py with -e.

• If the -f flag is specified multiple times, then the multiple functions will be registered.
• To register functions in regions other than the default region, you must use the function's full arn.
• Note: functions in different regions may lead to high billing rates for S3.