You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 1, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3

4
4
5
-
## Benefits
5
+
## Features
6
6
* HTTP & HTTPS support.
7
7
* No special software required. Just configure your system to use an HTTP proxy.
8
8
* 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
45
45
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:
46
46
47
47
* 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.
49
49
50
50
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.
51
51
@@ -58,15 +58,15 @@ The easiest way is to download a pre-built binary from the [GitHub Releases](htt
58
58
3. Configure your web browser (or OS) to use an HTTP proxy at the publicly accessible host running `awslambdaproxy` on port 8080.
59
59
60
60
## 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.
63
63
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 functionthat is created with a constantly running Lambda functionshould 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 functionthat 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.
66
66
67
67
## Future work
68
+
* Add security to proxy and tunnel connections
68
69
* Fix connections dropping each time a new tunnel is established
0 commit comments