Upgrades and support for VAC will finally end 1st January 2023. This will have been communicated to you by your Varnish representative but if you have any concerns or would like to discuss your options then please reach out to your Account Manager or firstname.lastname@example.org
Group Varnish instances in cluster groups, having a single point of management.
Edit and deploy VCL and Varnish parameters in one go
Real time and past data statistics with Varnish counters
Ban content from your(s) Varnish Cache instances with a single request.
Purging content, in one go from your Varnish instance(s) with the Super Fast Purger
Centralize VCL and Varnish parameters and keep them consistent through all the Varnish instances.
|VAC version||Varnish version||Varnish agent|
|3.9.3 latest||6.x latest||6.0 latest|
|3.8.3 or lower||4.1.x||4.1.x|
|3.8.3 or lower||4.0.x||4.0.x|
|3.8.3 or lower||3.x||3.x.x.|
VAC communicates with the Varnish Cache server(s) trough the Varnish Agent.
It is distributed as Debian/Ubuntu deb packages, Red Hat RPMs.
VAC has modest hardware requirements. A virtual machine with 1GB RAM and 10 GB disk space is sufficient for ordinary installations. As a rule of thumb estimate each instance to add around 300MB overhead
From version 3.0.3 and above the VAC requires Java Runtime Environment version 7 or above.
Note that VAC 3.0.0 and above will require varnish-agent 2.2.0 and above.
Earlier versions of the VAC, such as 2.0.x, is dependent on varnish-agent 1.16. Both are no longer supported.