3proxy - Secure HTTP, HTTPS and SOCKS Proxy

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Secure Forward Proxy on Amazon EC2 - Ready in Minutes 3proxy is a lightweight, single-daemon proxy server delivering HTTP, HTTPS, and SOCKS4/5 forward proxying. This AMI ships it fully installed and running under systemd on Amazon EC2, so a working proxy endpoint is listening within minutes of launch - no manual compilation, no configuration required to get started. HTTP/HTTPS forward proxy listens on port 3128 and the SOCKS proxy on port 1080, both managed by systemd for automatic restarts and clean logging. ## Secure by Default - Never an Open Relay Unlike many competing proxy AMIs that ship with default or no credentials, this image generates a unique proxy username and password on first boot. No default password is baked into the image. Proxy authentication is enforced: anonymous or wrong-password requests are rejected with HTTP 407 and carry no traffic. The default access control list allows authenticated clients only from loopback and private RFC1918 ranges, followed by a deny-all rule. HTTPS CONNECT tunnelling is restricted to standard TLS ports so the proxy cannot be abused to reach arbitrary destinations. The operating system ships fully patched with unattended security updates enabled. Compared to heavier alternatives like Squid-based AMIs or multi-component NGINX proxy stacks, 3proxy runs HTTP and SOCKS in a single small daemon with minimal resource overhead - ideal when you need a controlled egress point without the complexity of a full caching proxy. ## AWS Integration This AMI runs on Amazon EC2 and routes traffic through your Amazon VPC. Control inbound access using VPC Security Groups - open port 3128 or 1080 only to your client CIDR. Use AWS Systems Manager Session Manager for secure shell access without exposing SSH. Export proxy logs to Amazon CloudWatch Logs for centralized monitoring and alerting. ## Use Case: CI/CD Pipeline Egress Control A DevOps team running 30+ microservices on Amazon EC2 needs all outbound artifact downloads and API calls to route through a single authenticated hop to satisfy their network security policy. Deploy this AMI as a two-instance proxy tier in a private subnet, point application HTTP_PROXY and SOCKS_PROXY environment variables at the proxy endpoints, and gain a single auditable egress point with per-request authentication - no open relay risk, no complex configuration. Additional scenarios include giving applications a controlled, authenticated egress point, adding a SOCKS proxy for tools that require one, or building a small private forward-proxy tier for a startup's outbound traffic. ## Quick-Start Deployment 1. Launch the AMI on Amazon EC2 (t3.micro or larger recommended).

2. Retrieve the generated proxy username and password from the instance console log or by connecting via SSH/Session Manager and reading /etc/3proxy/passwd.

3. Configure your client application to use the instance's private IP on port 3128 (HTTP/HTTPS) or 1080 (SOCKS).

4. Verify connectivity with a test request - authenticated requests succeed, anonymous requests return HTTP 407.

5. To serve clients outside RFC1918 ranges, add your client CIDR to /etc/3proxy/3proxy.cfg and open the matching port in your VPC Security Group. Time to a working proxy: under 5 minutes from instance launch. ## Request a Guided Deployment Walkthrough Need help planning a multi-proxy tier or customizing the ACL for your environment? Contact cloudimg support to book a 15-minute deployment walkthrough tailored to your architecture. ## Licensing and Attribution This is a repackaged open source software product with additional charges for cloudimg support services. 3proxy is distributed under a BSD-style permissive license. cloudimg is not affiliated with or endorsed by the 3proxy project. All product and company names are trademarks or registered trademarks of their respective holders. The current release is 3proxy.