Resources and limitations for Node.js environments¶

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:

Resources¶

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

Also included are the following items:

• Cloud Platform pipelines feature
• A Git repository

Limitations¶

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 don’t 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 PCI and HIPAA compliance only.
• Node.js applications do not support nginx.config files. Redirection from http to https must be done at the WAF level.
• Cloud Platform Platform CDN is incompatible with Node.js applications.
• Node.js applications can’t generate certificate signing requests (CSRs) in the Cloud Platform user interface. For more details, see this known issue.
• You can’t activate multiple SSL certificates on the same environment on Node.js applications.
• Acquia doesn’t control the stdout and stderr log formats. The application manages and controls such formats.