Using an Elastic IP addresses


  • This feature is not yet available to applications running on Acquia Cloud Next technologies.
  • This feature is available for Cloud Platform Enterprise, Site Factory, and Cloud Platform Professional subscribers.

If your Cloud Platform application must communicate out to a remote service, and the service requires all sources of inbound connections to be allowlisted, Acquia can provision an Elastic IP address (EIP) on the application’s Drupal infrastructure.

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.

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


Application layer EIPs can impact your infrastructure’s ability to scale during periods of high traffic or elevated resource consumption. Although Acquia can efficiently provision more infrastructure capacity for your application in response to demand, Acquia can’t activate the extra capacity until the new EIPs associated with it can be added to your allowlist or other system.