Documentation

Squid Proxy

Pre-configured Squid caching proxy image with sensible defaults for outbound web filtering and bandwidth optimisation. Includes ACL templates, access logging, and hardened base OS. Available as VM images for all major cloud and virtualisation platforms, and as a container for Kubernetes workloads.

Overview

The CloudSOE Squid Proxy image provides a fully configured, production-ready deployment of Squid Proxy. Every image is built from a hardened base OS, follows CIS benchmarks where applicable, and includes monitoring hooks for enterprise observability stacks.

Images are tested against each supported platform before release. Updates are published as new image versions — the underlying application, language runtime, and OS packages are all kept current.

Requirements

Resource Minimum Recommended
CPU1 vCPU2 vCPUs
RAM1 GB2 GB
Disk10 GB20 GB
NetworkPublic or privatePrivate + floating IP / load balancer

For SonarQube images, increase RAM to a minimum of 2 GB (4 GB recommended) due to JVM and Elasticsearch memory requirements.

Quick Start

The fastest way to try Squid Proxy is with Docker: 

docker pull cloudsoe/squid-proxy:latest
docker run -d -p 8080:80 cloudsoe/squid-proxy:latest

For platform-specific instructions, see the deployment guides on the project page.

Configuration

Environment Variables

All CloudSOE images accept configuration through environment variables at boot time:

VariableDescriptionDefault
CLOUDSOE_TIMEZONESystem timezoneUTC
CLOUDSOE_AUTO_UPDATEEnable unattended security updatestrue
CLOUDSOE_MONITORINGEnable Prometheus node-exporterfalse
CLOUDSOE_LOG_LEVELApplication log verbositywarn

First-Boot Script

Every image ships with a setup helper at /opt/cloudsoe/setup-squid-proxy.sh. Running it interactively walks you through initial configuration: 

sudo /opt/cloudsoe/setup-squid-proxy.sh

For unattended installs, pass --auto and set the required environment variables beforehand.

File Locations

PathPurpose
/var/www/htmlWeb root (Apache / Nginx)
/etc/cloudsoe/CloudSOE configuration files
/opt/cloudsoe/Scripts and utilities
/var/log/cloudsoe/Image-specific logs

Supported Platforms

AWS Amazon Machine Images (AMIs) for EC2 deployments. Azure Virtual machine images for Microsoft Azure. Docker Container images for Docker and Docker Compose deployments. OpenStack Cloud infrastructure images built for OpenStack environments. OpenShift Container images and templates for Red Hat OpenShift. VMware Virtual machine images for VMware vSphere and ESXi. Vagrant Vagrant boxes for local development and testing environments.

Each platform has a dedicated deployment guide on the project page.

Security

  • Base OS hardened following CIS Level 1 benchmarks
  • SSH root login disabled — key-based auth only
  • Unattended security updates enabled by default
  • Minimal package set — no unnecessary services running
  • Firewall pre-configured to allow only required ports
  • File integrity monitoring via AIDE (Advanced Intrusion Detection Environment)

To report a security vulnerability, please email security@cloudsoe.com with details. Do not open a public issue.

Troubleshooting

Image won't boot

Check that the flavour / instance type meets the minimum requirements above. On OpenStack, verify the image was imported with the correct disk format (qcow2 for KVM, vmdk for VMware).

Cannot connect via SSH

  • Ensure port 22 is open in your security group / firewall rules
  • Use the correct username: ubuntu (not root)
  • Verify your SSH key was injected at launch time

Application not responding

Check the service status and logs:

sudo systemctl status cloudsoe-squid-proxy
sudo journalctl -u cloudsoe-squid-proxy --since "10 minutes ago"

Database connection errors

Verify the database service is running and that the credentials in your environment variables match. For Docker Compose deployments, ensure the depends_on directive is present so the database starts first.

Release History

No releases published yet.

See the full changelog for releases across all projects.