Due to Cloud Platform’s security and permissions requirements, you may experience incompatibilities with some applications and Drupal contributed modules.
Note
For information about modules that can be used with Cloud Platform, but that may require additional configuration, see Modules to use with caution on Cloud Platform.
Modules
The following Drupal contributed modules cannot be used with Cloud Platform-based websites:
| Module/App | Issue |
|---|---|
| Advanced Varnish | This module requires subscribers to replace Acquia’s default VCL with a companion custom Varnish configuration not supported on Cloud Platform. |
| ApacheSolr file | Subscribers can’t edit the solrconfig.xml file on Cloud Platform. |
| APC | Alternative PHP cache is not recommended on Cloud Platform. It stores data on a per-infrastructure basis, which can lead to different data being served by different infrastructure. It also uses memory that would otherwise be used by OPcache. We recommend using Memcached instead. |
| AutoSlave | The Cloud Platform interface is configured to detect the primary and subordinate infrastructure and handle failover situations. This module hardcodes the settings and can cause your infrastructure to read or write to the incorrect database. |
| Background Process | The Background Process Apache infrastructure status module isn’t compatible with Cloud Platform. |
| Backup and Migrate | Not supported on Cloud Platform. For more information, see Backup and Migrate module not supported on Cloud Platform. |
| 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 infrastructure. See Boost and Cloud Platform for more details. |
| CDN | The File Conveyor sub-module, specifically, is incompatible with Acquia Cloud. The distributed file system used by Cloud Platform 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 in the Cloud Platform interface. |
| 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 Cloud Platform. |
| 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. |
HTTP/2 Server Push | This module has reached End-of-Life and will not receive any further maintenance. The project page also recommends for uninstalling this module. |
| 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 Cloud Platform. |
| Monolog | The Monolog module uses a syslog configuration incompatible with Cloud Platform. You should avoid using this module and use the core Syslog module instead. |
| OptimizeDB | This module optimizes all database tables and displays its sizes which can cause locked tables and other performance problems for your website. |
| Pantheon Advanced Page Cache | This module is incompatible with Acquia Cloud, and might cause Drupal to output HTTP headers that are too large for Cloud Platform. This causes errors of type 500 that are difficult to troubleshoot. The equivalent functionality in Acquia Cloud is provided by the Acquia Purge module. For more information, see Installing Acquia Purge. |
| PDF to HTML node generator | This module provides integration with the pdftohtml php library. This module is not installable on Cloud Platform. |
| Role memory limit | This module overrides memory limits set in settings.php. |
| Serial Field | Serial is based on an auto_increment of 1. Cloud Platform 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 Cloud Platform. Other methods of achieving this functionality are SimpleSAMLphp or LDAP. |
| SimpleTest | SimpleTest is based on an auto_increment of 1. Cloud Platform uses an auto_increment of five. For more information, see this issue on Drupal.org. |
| 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. |
| 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 Cloud Platform applications. It will not work with Cloud Platform 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. |
| Varnish Purge | To purge Varnish under Acquia Cloud, you must disable this module and use the Acquia Purge module. For more information, see Installing Acquia Purge. |
| Views Filter Harmonizer | This module sets a SESSION cookie, preventing Varnish caching. |
| WebP | This Drupal module creates a WebP copy of image style derivatives to decrease loading times. WebP support is limited in Acquia Cloud. You can use WebP images in websites that are powered by Cloud Platform. However, the platform does not support using WebP with ImageMagick. Therefore, you might face issues with image resizing and cropping through Drupal image styles. For more information, see How to enable support for WebP images on Acquia Cloud. |
Applications
For information about other software that is incompatible with Cloud Platform, see Unsupported software.