Squid Proxy (Hardened) on Amazon Linux 2023

Squid caching proxy on Amazon Linux 2023, security-hardened for production: minimal package set, SSH key-only access, IMDSv2-only, and continuously patched images. This product has charges associated with it for image hardening, maintenance, and support.

View on AWS Marketplace

Why this image

• Production-ready: systemd-managed Squid; tune ACLs and cache in /etc/squid/squid.conf.
• Security-hardened at build time: minimal packages, key-only SSH, IMDSv2-only, proxy port firewalled to trusted CIDRs.
• Continuously patched: rebuilt, vulnerability-scanned, and republished on a regular cadence.

About

Squid Proxy (Hardened) on Amazon Linux 2023 is a production-ready, security-hardened image of the Squid caching and forwarding web proxy, maintained and supported by Derek Coleman & Associates Inc.

This is repackaged open-source software. Squid is developed by the Squid Project and is distributed under the GNU General Public License v2 or later. This product bundles unmodified upstream Squid on a hardened Amazon Linux 2023 base; the charges associated with this listing are for image hardening, continuous patching, vulnerability scanning, and business-day support - not for the underlying open-source software, which remains free.

Hardening baseline: minimal package footprint, SSH key-only access (password authentication disabled), IMDSv2 enforced, and a deny-all default proxy policy (Squid ships denying all client access; defining your ACLs in /etc/squid/squid.conf and opening TCP 3128 to trusted CIDRs is a deliberate customer configuration step, so the instance cannot be abused as an open proxy). Images are rebuilt, scanned for HIGH and CRITICAL vulnerabilities, and republished on a regular cadence so that new launches start current. Manage the service with systemd: sudo systemctl restart squid.

Pricing (hourly usage, AWS Marketplace)

Recommended: c7i.xlarge. AWS infrastructure charges are separate and billed by AWS. Charges stop when instances are terminated. No subscription, no minimum.

Getting started

1. Launch from AWS Marketplace (1-Click or EC2 console).
2. Connect via SSH with your EC2 key pair: ssh -i <key> ec2-user@<public-ip>. Root login is disabled; use sudo.
3. Edit /etc/squid/squid.conf to set your ACLs (Squid denies all by default), then: sudo systemctl restart squid, and open TCP 3128 to trusted CIDRs only.
4. Verify: sudo systemctl status squid.
5. Sensitive data: there are no passwords or secrets anywhere in this product. Logs under /var/log may contain client IPs - treat as personal data.
6. Backup: snapshot the EBS volume (it contains all configuration and data).
7. Resources: a single instance uses 1 EC2 instance and 1 gp3 EBS volume; no other AWS resources are created.
8. Support: support@dcassociatesgroup.com.

Support

Email support@dcassociatesgroup.com — business-day response. Covers image operation, the hardening baseline, and launch issues. See support.