Skip to content
Squid Caching Proxy Server product logo
  • AWSAvailable on Amazon Web Services
  • Azure· soonComing soon on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Available

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, identical on every cloud it ships on. 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 and Azure.

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.

  1. AWS
    Available

    Amazon Web Services

    AMI · v6.14

    AWS AMI ID

    Shown 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
    • 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
    Launch on AWS MarketplaceAWS launch steps

    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.

  2. Azure
    Coming soon

    Microsoft Azure

    Compute Gallery image · v6.14

    Azure Compute Gallery image ID
    …/galleries/provencloud_marketplace/images/squid/versions/2026.11.1
    Released
    OS disk
    Premium_LRS · 30 GiB
    Gallery
    provencloud_marketplace
    Definition
    squid
    Resource group
    provencloud-marketplace-rg
    VM sizes
    • Standard_D2as_v7
    • Standard_D2as_v5
    • Standard_B2ms
    • Standard_D4as_v7
    Regions50 regions· show all
    • eastus
    • australiacentral
    • australiaeast
    • australiasoutheast
    • austriaeast
    • belgiumcentral
    • brazilsouth
    • canadacentral
    • canadaeast
    • centralindia
    • centralus
    • chilecentral
    • denmarkeast
    • eastasia
    • eastus2
    • francecentral
    • germanywestcentral
    • indiasouthcentral
    • indonesiacentral
    • israelcentral
    • italynorth
    • japaneast
    • japanwest
    • jioindiawest
    • koreacentral
    • koreasouth
    • malaysiawest
    • mexicocentral
    • newzealandnorth
    • northcentralus
    • northeurope
    • norwayeast
    • polandcentral
    • qatarcentral
    • southafricanorth
    • southcentralus
    • southeastasia
    • southindia
    • spaincentral
    • swedencentral
    • switzerlandnorth
    • uaenorth
    • uksouth
    • ukwest
    • westcentralus
    • westeurope
    • westindia
    • westus
    • westus2
    • westus3
    Azure launch steps
AWS

Getting started on Amazon Web Services

From launch to signed in, step by step.

  1. Subscribe on AWS Marketplace and launch in your region with TCP 3128 open only to the addresses that will use the proxy (never 0.0.0.0/0), plus 22, 80 and 8000; wait a few minutes for first boot.

  2. Port 3128 is a proxy, not a web page: set http://<instance-public-ip>:3128 as the HTTP and HTTPS proxy in your browser, system or tool, with username proxyuser and your EC2 Instance ID typed with a capital leading I as the password (for example I-0123456789abcdef0).

  3. Test it: curl -x http://<instance-public-ip>:3128 --proxy-user proxyuser:<password> https://checkip.amazonaws.com prints the proxy's IP. The landing page at http://<instance-public-ip>/ repeats these details.

  4. Webmin is on port 8000 with username admin and the same capital-I password. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_proxy.sh or pass_webmin.sh, manage users with proxy_users.sh, and check the server with sudo squid-status.

Security posture

What this AWS 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.

Azure

Getting started on Microsoft Azure

From launch to signed in, step by step.

  1. Create the VM from the Azure Marketplace listing with TCP 22, 80, 3128 and 8000 open in your network security group. Choose ubuntu as the administrator username so SSH and the script paths match, and wait a few minutes for first boot to finish.

  2. Set your browser or tool to use <vm-public-ip>:3128 as its HTTP proxy, with username proxyuser. The password is VM- followed by your VM ID (Azure portal > the virtual machine > Properties > VM ID, for example 02aab8a4-74ef-476e-8182-f6d2ba4166a6). Webmin (port 8000, user admin) uses the same password. Change it any time with sudo bash ~/iscripts/pass_proxy.sh.

  3. For production, limit admin ports to your own IP address.

Security posture

What this Azure image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image from the Azure Marketplace: every component comes from its own official source and no third-party image was launched or copied.

  • No two VMs share a login: first boot sets every password and secret key from the new VM's own vmId (read from Azure IMDS) or from fresh random values, and creates new SSH host keys.

  • The ubuntu login account ships password-locked with an empty authorized_keys, and Azure installs your own SSH key at deploy time.

  • Shell history, logs and cloud-init state are cleared before capture, and the image carries every Ubuntu 24.04 LTS security update with nothing pending.

  • Each gallery version is deployed as a Trusted Launch VM and checked against Microsoft's documented Linux certification test cases, the product's own end-to-end login tests and a stop/start cycle before it is published.

  • Restrict port 22 and the admin consoles to trusted IP ranges, and put public web consoles behind HTTPS with your own certificate.