Node JS

Resources and limitations for Node.js environments

This documentation page describes the specific resources available for your use in Cloud Platform Node.js application environments, and the current limitations of the environment types. For information about software resources included with Cloud Platform environments, and resources included with other related features, see Additional stack information.

Application sizes

Node.js applications have three sizes: Small, Medium, and Large. Each application size has a corresponding production environment and a Small development environment. The environment sizes have the following limits:

FeatureDevelopment - SmallProduction - SmallProduction - MediumProduction - Large
Max number of processes44812
Max RAM per process (GB)1.875 (7.5 total)1.875 (7.5 total)1.875 (15 total)1.875 (22.5 total)


Each environment in a Node.js application includes the following components:

Web server OSUbuntu 16.04
Load balancerNginx 1.12.1
Node.js18, 20 (With latest security updates)
Google Chrome117.0.5938.149 (compatible with Puppeteer v21.3.7)


To request a version of Node.js for your environment other than the default, create a Support ticket.

Also included are the following items:


Node.js environments in Cloud Platform have the following limitations:

  • Elastic IP Addresses (EIPs) are not supported on production and non-production environments.
  • Non-production environments are shared resources, and are subject to unexpected relaunches.
  • The following features are not supported:
    • Shield
    • SSH access into infrastructure
    • Varnish® or custom VCLs
    • Memcached
    • CD environments
  • Node.js applications do not contain a supported database service or file system asset manager, but you can connect to an external file system/ database service, such as a Drupal website.
  • Node.js applications can expose only one port, indicated by process.env.PORT, which is set by Acquia and cannot be overridden. You can, however, use websockets to handle multiple concurrent connections.
  • Node.js hosting supports FedRAMP, PCI, and HIPAA compliance only.
  • Node.js applications on Cloud Platform do not support custom nginx.config files. Redirection from http to https must be done at the WAF level, or through the Node.js environment by using X-Forwarded-Proto request header.
  • Node.js applications can not generate certificate signing requests (CSRs) in the Cloud Platform user interface. For more details, see this known issue.
  • You can not activate multiple SSL certificates on the same environment on Node.js applications.
  • Acquia does not control the stdout and stderr log formats. The application manages and controls such formats.
  • Node.js environments in Cloud Platform do not support on-demand revalidation of Next.js applications. On-demand revalidation might result in unexpected responses and intermittent 404 errors. Customers can use full rebuild, or keep a lower time-to-live (TTL) value for quicker cache refresh. This limitation does not apply to XXS t-shirt size, that is, 1-process environments.
  • Classic Node.js environments in Cloud Platform do not support static site generation.