IP address allowlisting controls access to Cloud Platform resources after requests originate from non-allowlisted IP addresses. The allowlist applies to the following services:
Cloud Platform user interface: You must allowlist your IP address to use the page, as it relies on platform APIs.
API-based access: All direct calls to Cloud Platform endpoints, such as https://cloud.acguia.com/api
Traffic to your hosted websites is not restricted by this feature. Site visitors can access your applications regardless of their IP address.
Automated processes that call APIs from outside your corporate network or VPN are blocked unless you allowlist their egress IP addresses. These processes include:
Continuous Integration/Continuous Deployment (CI/CD) runners and pipelines
External monitoring and health-check services
Custom automation scripts and batch jobs
To fix an integration that stops working after you enable allowlisting:
Identify the public egress IP address of the integration.
Add the IP address to the allowlist.
Use static IP addresses: If your integration runs from a cloud provider with dynamic IP addresses, use a stable egress strategy, such as a Network Address Translation (NAT) gateway or static egress, and allowlist that specific IP address.
Only users who have the Owner (glossary term, activate to view definition) or Administrator (glossary term, activate to view definition) role for an application’s organization can enable or disable IP address allowlisting for an application.
To enable IP address allowlisting:
If you must allowlist Acquia’s IP addresses for your websites or services, create a Support ticket to obtain the necessary information.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
IP address allowlisting controls access to Cloud Platform resources after requests originate from non-allowlisted IP addresses. The allowlist applies to the following services:
Cloud Platform user interface: You must allowlist your IP address to use the page, as it relies on platform APIs.
API-based access: All direct calls to Cloud Platform endpoints, such as https://cloud.acguia.com/api
Traffic to your hosted websites is not restricted by this feature. Site visitors can access your applications regardless of their IP address.
Automated processes that call APIs from outside your corporate network or VPN are blocked unless you allowlist their egress IP addresses. These processes include:
Continuous Integration/Continuous Deployment (CI/CD) runners and pipelines
External monitoring and health-check services
Custom automation scripts and batch jobs
To fix an integration that stops working after you enable allowlisting:
Identify the public egress IP address of the integration.
Add the IP address to the allowlist.
Use static IP addresses: If your integration runs from a cloud provider with dynamic IP addresses, use a stable egress strategy, such as a Network Address Translation (NAT) gateway or static egress, and allowlist that specific IP address.
Only users who have the Owner (glossary term, activate to view definition) or Administrator (glossary term, activate to view definition) role for an application’s organization can enable or disable IP address allowlisting for an application.
To enable IP address allowlisting:
If you must allowlist Acquia’s IP addresses for your websites or services, create a Support ticket to obtain the necessary information.
If this content did not answer your questions, try searching or contacting our support team for further assistance.