This page applies only to Cloud Classic. To access the documentation, select Cloud Classic from the infrastructure list.

Environments running on Cloud Platform technologies, use Web EIPs.

For Cloud Platform Enterprise, Site Factory and Cloud Platform Professional subscribers, Acquia can provision an Elastic IP address (EIP) on the Cloud Classic application’s Drupal infrastructure when:

• The application must communicate to a remote service
• The service requires all sources of inbound connections to be allowlisted

Without EIPs, the IP addresses associated with Acquia’s application infrastructure are subject to change at any time. Typically, EIPs are only required when you must integrate your application with a remote single sign-on (SSO) solution, or a third-party service requiring allowlisted static IP addresses.

EIPs persist when the Cloud Platform infrastructure undergoes certain types of maintenance, but will be lost if dedicated infrastructure is removed.

This page applies only to Cloud Classic. To access the documentation, select Cloud Classic from the infrastructure list.

Environments running on Cloud Platform technologies, use Web EIPs.

For Cloud Platform Enterprise, Site Factory and Cloud Platform Professional subscribers, Acquia can provision an Elastic IP address (EIP) on the Cloud Classic application’s Drupal infrastructure when:

• The application must communicate to a remote service
• The service requires all sources of inbound connections to be allowlisted

Without EIPs, the IP addresses associated with Acquia’s application infrastructure are subject to change at any time. Typically, EIPs are only required when you must integrate your application with a remote single sign-on (SSO) solution, or a third-party service requiring allowlisted static IP addresses.

EIPs persist when the Cloud Platform infrastructure undergoes certain types of maintenance, but will be lost if dedicated infrastructure is removed.