Skip to content
This repository was archived by the owner on Nov 1, 2025. It is now read-only.

Commit 84b9bee

Browse files
author
Dan Vittegleo
committed
update readme
1 parent 910addd commit 84b9bee

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
![](/images/overview.gif?raw=true)
44

5-
## Benefits
5+
## Features
66
* HTTP & HTTPS support.
77
* No special software required. Just configure your system to use an HTTP proxy.
88
* Each AWS Lambda region provides 1 outgoing IP address that gets rotated roughly every 4 hours. That means if you use 10 AWS regions, you'll get 60 unique IPs per day.
@@ -45,7 +45,7 @@ The easiest way is to download a pre-built binary from the [GitHub Releases](htt
4545
1. Copy `awslambdaproxy` binary to a publicly accessible linux host (e.g. EC2 instance). You will need to open the following ports on this host:
4646

4747
* Port 8080 - this port listens for user proxy connections and needs to only be opened to whatever your external IP address is where you plan to browse the web.
48-
* Port 8081 - this port listens for tunnel connections from executing Lambda functions and needs to be opened to the world. This is a security concern and ideally will be locked down in the future.
48+
* Port 8081 - this port listens for tunnel connections from executing Lambda functions and needs to be opened to the world. This is a security concern and will be locked down in the future.
4949

5050
2. On publicly accessible host, run `awslambdaproxy`. You'll need to ensure AWS access key and secret key environment variables are defined. For now, this access key should have AdministratorAccess.
5151

@@ -58,15 +58,15 @@ The easiest way is to download a pre-built binary from the [GitHub Releases](htt
5858
3. Configure your web browser (or OS) to use an HTTP proxy at the publicly accessible host running `awslambdaproxy` on port 8080.
5959

6060
## FAQ
61-
1. <b>Should I use this?</b> That's up to you. Use at your own risk.
62-
2. <b>Will this make me completely anonymous</b> No, absolutely not. The goal of this project is just to obfuscate your web traffic by rotating your IP address. All of your traffic is going through AWS which could be traced back to your account. You can also be tracked still with [browser fingerprinting](https://panopticlick.eff.org/), etc.
61+
1. <b>Should I use awslambdaproxy?</b> That's up to you. Use at your own risk.
62+
2. <b>Will this make me completely anonymous?</b> No, absolutely not. The goal of this project is just to obfuscate your web traffic by rotating your IP address. All of your traffic is going through AWS which could be traced back to your account. You can also be tracked still with [browser fingerprinting](https://panopticlick.eff.org/), etc.
6363
3. <b>How often will my external IP address change?</b> For each region specified, the IP address will change roughly every 4 hours. This of course is subject to change at any moment as this is not something that is documented by AWS Lambda.
64-
4. <b>How big is the pool of IP addresses?</b> This I don't know, but I did not have a duplicate IP while running the proxy for a week.
65-
5. <b>How much does this cost?</b> awslambdaproxy should be able to run mostly on the AWS free tier minus bandwidth costs. It can run on a t2.micro instance and the default configuration 128MB Lambda function that is created with a constantly running Lambda function should also fall in the free tier usage. The bandwidth is what will cost you money. You will pay for bandwidth usage for both EC2 and Lambda.
64+
4. <b>How big is the pool of IP addresses?</b> This I don't know, but I do know I did not have a duplicate IP while running the proxy for a week.
65+
5. <b>How much does this cost?</b> awslambdaproxy should be able to run mostly on the [AWS free tier](https://aws.amazon.com/free/) minus bandwidth costs. It can run on a t2.micro instance and the default 128MB Lambda function that is constantly running should also fall in the free tier usage. The bandwidth is what will cost you money; you will pay for bandwidth usage for both EC2 and Lambda.
6666

6767
## Future work
68+
* Add security to proxy and tunnel connections
6869
* Fix connections dropping each time a new tunnel is established
70+
* Create minimal IAM policy
6971
* Rewrite code to be testable
7072
* Write tests
71-
* Add security to proxy and tunnel connections
72-
* Create minimal IAM policy

0 commit comments

Comments
 (0)