If your Cloud Next application must communicate to a remote service, and the service requires inbound connections to come from static and known IP addresses, Acquia can provision Web Elastic IP addresses (Web EIPs) for your application environments.

Without Web EIPs, the IP addresses associated with Cloud Next’s infrastructure are subject to change at any time.

Features of Web EIPs

• Outbound requests come from dedicated IP addresses:

  Web EIPs are designed for applications that must make external requests to services that require allowlisted-inbound connections.

• No application changes are needed:

  When making requests to external services, Web EIPs are automatically utilized.

• Dedicated IP addresses through autoscaling and periods of high traffic or elevated resource consumption:

  Web EIPs that are assigned to the application environment persist even after your application scales, eliminating the need to edit IP allowlists before extra capacity can be used at Acquia.

Limitations

• Non-Drupal applications, PHP scripts, and third-party libraries are not supported:

  Acquia does not support custom integrations.

Viewing your Web EIPs in the Cloud Platform user interface

To view your Web EIPs:

• Sign in to the Cloud Platform user interface and select your application and environment.

• In the navigation pane, click Infrastructure.

  The Infrastructure page displays the Web EIPs for the application environment:

Web EIP compatibility

Web EIPs are compatible with the APIs provided by Drupal core for making requests to external services, such as:

• drupal_http_request() in Drupal 7
• Drupal::httpClient in the current Drupal version

Additional supported protocols and libraries include:

• file_get_contents() and PHP streams
• curl command line utility and PHP library
• wget command line utility
• Log forwarding
• SMTP
• LDAP
• SSH/SFTP
• MySQL

Using Web Elastic IP addresses