Cloud Platform

CD environment resources and limitations


This page applies only to Cloud Platform CD environments. Other environments, such as Cloud Platform, Pipelines, and Cloud IDE, may provide different resources.

Each Cloud Platform CD on-demand environment includes the following resources:

For information about software resources included with Cloud Platform environments, and resources included with other related features, see Additional stack information.



CD environments in Cloud Platform are not meant to be used with production data or to store production data, especially if your application must adhere to compliance standards, such as PCI, HIPAA, or FedRAMP.

CD environments in Cloud Platform are not intended as replacements for production or load testing environments. The following limitations apply to CD environments:

  • CD environments are limited to three active databases per environment limited to 1 GB, and query execution time is limited to 60 seconds.

  • You cannot add or delete databases in Cloud Platform CD environments. To retrieve a new database, you must recreate the environment.

  • CD environment software versions might not match Cloud Platform environment versions. Pushing applications from your CD environment to your production environment can have unexpected consequences. In general, issues should be minimal.

  • Currently, CD environments do not support the following features available to standard Cloud Platform environments:

    • Creation of custom cron jobs

    • Live development

    • Infrastructure or uptime reporting

    • Custom VCLs

    • Dedicated Acquia Search cores

    • mod_proxy configurations—tests depending on mod_proxy enablement fails

    • Node.js environments

    • Elastic IPs (EIPs)

  • To maintain platform stability, CD environments exceeding filesystem limits are subject to deletion.

  • CD environments are limited to a maximum PHP memory limit of 1024 MB .


    If you increase the memory limit to 1024 MB, your application might experience out-of-memory or performance issues.

  • Acquia performs 24x7 monitoring of CD environment infrastructure health but, unlike Cloud Platform Enterprise production environments, the application uptime SLA does not extend to CD environments.

  • Since Cloud Platform CD is based on a dynamic infrastructure, the following items are applicable to CD environments:

    • Acquia proactively performs service restarts or maintenance activities to preserve high availability. Service restarts or maintenance activities are not preceded by formal notifications and occur as required to maintain service availability.

    • Acquia might terminate cron jobs and other automated processes at its discretion; therefore, customer scripts must be resilient to failure.

    • SSH sessions are disconnected when containers are replaced. In such cases, you must reconnect to a healthy container.

  • Applications with Cloud Shield or Secure VPN can utilize CD environments, but they are provisioned in a shared VPC in the nearest supported region.

  • CD environment clusters are located in the following AWS regions:

    us-east-1, eu-west-1, and ap-southeast-2

  • CD environments support a maximum of 64 MB of Memcache memory. If your application has the Memcache memory higher than this limit, your staging or production stack might run into Memcache limitation issues.

    Workaround: You can update the settings.php file to disable Memcache for CD environments.