
- AWSAvailable on Amazon Web Services
- Azure· soonComing soon on Microsoft Azure
- GCP· nextGoogle Cloud is next on the roadmap
Squid Caching Proxy Server
Squid 6.14 caching web proxy with Webmin on Ubuntu 24.04 LTS, closed by default: every request needs a proxy username and password, and anything not explicitly allowed is denied. Give servers in private networks one controlled way out to the internet, send traffic through a single fixed IP address, and save bandwidth by caching repeated downloads. Proxy users are added or removed with one command.
- Version
- v6.14
- Operating system
- Ubuntu 24.04 LTS
- Architecture
- x86_64
- Support
- Email support
What's installed
Every package and version on the image. Nothing else is installed.
- Squid 6.14
- nginx 1.24.0 (landing page only)
- apache2-utils (htpasswd)
- Webmin 2.670
LicensingOpen source (GPL-2.0), no licence key required
Deploy anywhere
Squid Caching Proxy Server on AWS.
Google Cloud is next on the roadmap. One clean-room build, one first-boot credential model, one patch cadence — identical on every cloud you run. Every identifier below is the real one; copy it and launch.
- AWSAvailable
Amazon Web Services
AMI · v6.14
AWS AMI IDShown for your region on the AWS Marketplace launch page once you subscribe.
- Released
- Root volume
- gp3 · 30 GiB
Instance types- t3a.small
- t3.small
- t3a.medium
- m6a.large
Regions34 regions· show all· hide
- us-east-1
- af-south-1
- ap-east-1
- ap-east-2
- ap-northeast-1
- ap-northeast-2
- ap-northeast-3
- ap-south-1
- ap-south-2
- ap-southeast-1
- ap-southeast-2
- ap-southeast-3
- ap-southeast-4
- ap-southeast-5
- ap-southeast-6
- ap-southeast-7
- ca-central-1
- ca-west-1
- eu-central-1
- eu-central-2
- eu-north-1
- eu-south-1
- eu-south-2
- eu-west-1
- eu-west-2
- eu-west-3
- il-central-1
- me-central-1
- me-south-1
- mx-central-1
- sa-east-1
- us-east-2
- us-west-1
- us-west-2
5-day free trial, then from $0.03/hr software charge (larger instance sizes cost more) plus your own EC2 costs, billed by AWS.
Subscriptions are open to AWS India (AISPL) accounts. Outside India? Ask us for a private build.
Getting started
From launch to signed in, step by step.
Subscribe on AWS Marketplace and launch in your region with TCP
3128open only to the addresses that will use the proxy (never0.0.0.0/0), plus22,80and8000; wait a few minutes for first boot.Port
3128is a proxy, not a web page: sethttp://<instance-public-ip>:3128as the HTTP and HTTPS proxy in your browser, system or tool, with usernameproxyuserand your EC2 Instance ID typed with a capital leading I as the password (for exampleI-0123456789abcdef0).Test it:
curl -x http://<instance-public-ip>:3128 --proxy-user proxyuser:<password> https://checkip.amazonaws.comprints the proxy's IP. The landing page athttp://<instance-public-ip>/repeats these details.Webmin is on port
8000with usernameadminand the same capital-I password. SSH asubuntuwith your key pair. Change passwords withsudo bash /home/ubuntu/iscripts/pass_proxy.shorpass_webmin.sh, manage users withproxy_users.sh, and check the server withsudo squid-status.
Security posture
What this image does and does not ship with, one fact per line.
Clean-room build on Canonical's official Ubuntu 24.04 LTS image: every component comes from its own official source, and nothing is copied from any third-party image.
Squid comes from Ubuntu's own repository with all security updates applied.
No credentials ship in the image: on first boot every instance sets its own proxy and Webmin passwords from EC2 instance metadata (IMDSv2) and creates its own server keys.
Every request must authenticate, and the access list denies everything not explicitly allowed.
Requests to the instance metadata service over IPv4 and IPv6 and to link-local addresses are blocked, so the proxy cannot be used to read the server's own credentials.
SSH is key-only, and build-time SSH keys, host keys, machine ID, shell history and logs were removed before imaging.
The bundled password tools enforce at least 10 characters with upper- and lower-case letters, a number and a symbol.
Open port 3128 only to the networks that need it, and restrict ports 22 and 8000 to trusted IP ranges in your security group.