Build 50+ EC2 Proxy Servers
Budget: ₹1,500 – ₹12,500 INR
I want to spin up a pool of at least fifty Ubuntu-based proxies on AWS EC2 and bind each one to an IP from my own range. Every proxy has to authenticate with the classic username:password pair, stay online without random drops, and be ready the moment you hand them over.
Ips must be 40 series
40.192.108.36:8000:naveen:naveen
40.192.89.249:8000:naveen:naveen for reference.
Here’s what I need you to take care of:
• Launch the instances on my AWS account (I’ll provide access with the proper IAM role).
• Attach the correct IPs from my series, confirm they route properly, and keep them fixed to each proxy.
• Install and configure the proxy service of your choice—Squid, 3proxy or another proven option—as long as it supports per-user authentication and logs minimal data.
• Harden each server (UFW, fail2ban, SSH hardening, basic CloudWatch alarms) so the network stays clean and stable.
• Hand back a simple CSV listing IP, port, username, and password for every proxy, plus a quick README so I can recreate or scale the setup later.
I’ve chosen EC2 and Ubuntu because they’re flexible and familiar; feel free to suggest instance types or sizing that best balance cost and reliability. When you reply, focus on the relevant experience you have building authenticated proxies on AWS—brief but specific examples are enough.
Once we confirm the plan, I expect the full block of proxies operational within a few days.
Requirements:
Deploy 50+ proxies on AWS (EC2 or equivalent) using provided IP series.
Each proxy must have unique IP:port and user:pass auth.
Proxies must be reliable, low-latency, and secure.
Deliver a working list of proxies in the format IP:PORT:USER:PASS.
Provide a simple setup script or clear instructions so I can recreate/scale later.
Brief testing proof (e.g., curl or browser test) for several proxies.
Ips must be 40 series
40.192.108.36:8000:naveen:naveen
40.192.89.249:8000:naveen:naveen for reference.
Here’s what I need you to take care of:
• Launch the instances on my AWS account (I’ll provide access with the proper IAM role).
• Attach the correct IPs from my series, confirm they route properly, and keep them fixed to each proxy.
• Install and configure the proxy service of your choice—Squid, 3proxy or another proven option—as long as it supports per-user authentication and logs minimal data.
• Harden each server (UFW, fail2ban, SSH hardening, basic CloudWatch alarms) so the network stays clean and stable.
• Hand back a simple CSV listing IP, port, username, and password for every proxy, plus a quick README so I can recreate or scale the setup later.
I’ve chosen EC2 and Ubuntu because they’re flexible and familiar; feel free to suggest instance types or sizing that best balance cost and reliability. When you reply, focus on the relevant experience you have building authenticated proxies on AWS—brief but specific examples are enough.
Once we confirm the plan, I expect the full block of proxies operational within a few days.
Requirements:
Deploy 50+ proxies on AWS (EC2 or equivalent) using provided IP series.
Each proxy must have unique IP:port and user:pass auth.
Proxies must be reliable, low-latency, and secure.
Deliver a working list of proxies in the format IP:PORT:USER:PASS.
Provide a simple setup script or clear instructions so I can recreate/scale later.
Brief testing proof (e.g., curl or browser test) for several proxies.
Related categories:
System Admin
Linux
Amazon Web Services
Ubuntu
Scripting
Network Security
Network Monitoring
System Administration