Information for: DEVELOPERS   PARTNERS

Modules and applications incompatible with Acquia Cloud

Acquia Cloud module and application issues

The Acquia Cloud platform and security require permissions and installs to be built in a particular fashion. This can sometimes cause incompatibilities with Drupal contributed modules.


For information on other software that is incompatible with Acquia Cloud, see Unsupported software.

Module/App Issue
Advanced Varnish This module requires subscribers to replace Acquia’s default VCL with a companion custom Varnish configuration not supported on Acquia Cloud.
ApacheSolr file Subscribers can’t edit the solrconfig.xml file on Acquia Cloud.
APC Alternative PHP cache is not recommended on Acquia Cloud. It stores data on a per-server basis, which can lead to different data being served by different servers. It also uses memory that would otherwise be used by OPcache. We recommend using Memcached instead.
AutoSlave The Acquia Cloud platform is configured to detect the primary and subordinate servers and handle failover situations. This module hardcodes the settings and can cause your server to read or write to the incorrect database.
Background Process The Background Process Apache server status module is not compatible with the Acquia Cloud platform.
Backup and Migrate Not supported on Acquia Cloud. For more information, see Backup and Migrate module not supported on Acquia Cloud.
Block Cache Alter This module causes issues with caching, and has not been updated in several years. It is not recommended for use.
Boost This creates many disk writes, which can cause problems on shared servers. See Boost and Acquia Cloud for more details.
CDN The File Conveyor sub-module, specifically, is incompatible with Acquia Cloud. The distributed file system used by Acquia Cloud Enterprise doesn’t support inotify, which this module requires for operation. This is related to content delivery networks (CDNs) and using Origin Pull mode will still work.
CiviCRM CiviCRM is dependent on stored procedures and triggers that do not work on the Acquia Cloud platform.
CloudFlare Purge (cfpurge) This module includes API limits that may prevent users from viewing updated content on your website. Instead, Acquia recommends the use of Acquia Purge.
Configuration Management This module requires a writeable directory that is also trackable at the same time by Git; this approach isn’t possible on Acquia Cloud.
Facebook Connect Require session cookies to be set, preventing Varnish® from caching pages.
File Cache The File Cache module moves caching to the file system, which can cause major load on the distributed file system and can cause the site (or multiple sites in the case of shared hosting) to go down.
Global Filter Sets session cookies to filter views, which prevents Varnish from caching pages.
H5P The H5P module sets session cookies for anonymous visitors using pages that contain H5P elements. This results in all future requests for those anonymous users to bypass Varnish caching.
IP Geolocation Views & Maps Require session cookies to be set, preventing Varnish from caching pages.
Memcache Storage Although not incompatible, Acquia discourages using this module’s due to its developer’s limited updates. Instead, Acquia encourages the use of the Memcache API and Integration module, which integrates better with Acquia’s memcached implementation.
Mobile Tools Mobile Tools prevents the use of Varnish. See Enabling device-based redirects for other options that work with Acquia Cloud.
reCAPTCHA Require session cookies to be set, preventing Varnish from caching pages.
Role memory limit This module overrides memory limits set in settings.php.
Serial Field Serial is based on an auto_increment of 1. Acquia Cloud uses an auto_increment of five.
Session API Requires session cookies to be set, preventing Varnish from caching pages.
Session API sets cookies on the user. When using this module, cron can run intense queries to join the session and session_api tables, causing major slowdowns.
Session Cache API This module is generally incompatible with Varnish caching. It may also cause file system performance issues.
Shibboleth Authentication Shibboleth is not supported on Acquia Cloud. Other methods of achieving this functionality are SimpleSAMLphp or LDAP.
SimpleTest SimpleTest is based on an auto_increment of 1. Acquia Cloud uses an auto_increment of five. For more information, see this issue on
Smart IP This module can be configured to set session cookies for anonymous users, making it incompatible with Varnish.
Supercookie Stores sessions outside of the session table, and sets No-Cache headers. This module is also incompatible with Varnish.
TB Mega Menu This module can cause performance problems for your website and is not covered by Drupal’s security policy. If it must be used, patch the module to reduce calls made to your website’s database.
Text Size Require session cookies to be set, preventing Varnish from caching pages.
Varnish This Drupal module attempts to replicate the effort of the Varnish Cache that is already available to Acquia Cloud applications. It will not work with Acquia Cloud applications because it requires connections to the load balancers, which Acquia does not provide. The Varnish caching provided by Acquia works out of the box, as long as you use caching.
Views Filter Harmonizer This module sets a SESSION cookie, preventing Varnish caching.