CD environment resources and limitations

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

  • Multi-tier Varnish®, web, and database configuration
  • Compatibility with Drupal 7 and Drupal 9
  • Up to 5 GB of filesystem storage
  • Two dedicated PHP processes
  • Memcache
  • Supports custom domain names
  • Supports SSL

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 aren’t 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 aren’t 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 can’t add or delete databases in Cloud Platform CD environments. To retrieve a new database, you must recreate the environment.
  • CD environment software versions may not match Cloud Platform environment versions. Pushing applications from your CD environment to your Production environment may have unexpected consequences. In general, issues should be minimal.
  • CD environments don’t currently support the following features available to standard Cloud Platform environments:
    • Creation of custom cron jobs
    • Live Development
    • Infrastructure or uptime reporting
    • Custom VCLs
    • Drupal 6-based environments
    • Dedicated Acquia Search cores
    • mod_proxy configurations—tests depending on mod_proxy enablement will fail
    • Node.js environments
    • Elastic IPs (EIPs) can’t be assigned to CD environments
  • To maintain platform stability, CD environments exceeding filesystem limits are subject to deletion.
  • CD environments are limited to a 256 MB PHP memory limit.
  • Acquia performs 24x7 monitoring of CD environment infrastructure health but, unlike Cloud Platform Enterprise production environments, the application uptime SLA doesn’t extend to CD environments.
  • Since Cloud Platform CD is based on a dynamic infrastructure, the following items are applicable to CD environments:
    • Acquia will proactively perform service restarts or maintenance activities to preserve High Availability. Service restarts or maintenance activities won’t be preceded by formal notifications and will occur as required to maintain service availability.
    • Acquia may terminate cron jobs and other automated processes at its discretion; therefore, customer scripts must be resilient to failure.
    • SSH sessions will be disconnected when containers are replaced; in such cases, customers must reconnect, and they will connect to a healthy container.
  • Applications with Cloud Shield or Secure VPN can utilize CD Environments, but they will always be 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.