---
title: "Using mod_proxy on Cloud Next"
date: "2024-02-14T06:18:38+00:00"
summary: "Easily configure mod_proxy on Cloud Next for complex websites. Learn how to enable, disable, and manage proxy settings through the Cloud Platform UI. Understand considerations and best practices for optimal performance."
image:
type: "page"
url: "/acquia-cloud-platform/using-modproxy-cloud-next"
id: "bfcd74de-2245-4263-b466-172c33cdf0fa"
---

Note

This feature is available only on environments running on [Cloud Next](/acquia-cloud-platform) technologies. For using mod\_proxy on the Cloud Classic infrastructure, [contact Acquia Support](/service-offerings/support#contact-acquia-support).

Complex websites are often handled by multiple web servers, all containing the same code. Sometimes it can be necessary to split a website into multiple applications, all served from the same domain. The primary way of handling multiple, separate websites served under a single domain is to use a proxy server. A proxy server is usually another server that handles requests from resources on servers by clients.

For more information on the different proxies available on Cloud Platform, see [Proxies and Acquia Cloud](https://acquia.my.site.com/s/article/360005458614-Proxies-and-Acquia-Cloud).

You can implement a mod\_proxy configuration by using Apache's [mod\_proxy](http://httpd.apache.org/docs/current/mod/mod_proxy.html) module on Cloud Platform. You can manage mod\_proxy on each environment by using the self-service [configuration settings](/acquia-cloud-platform/manage-apps/configure) in the Cloud Platform user interface. 

With this feature, you can:

*   Enable or disable mod\_proxy through the Cloud Platform user interface.
*   Configure mod\_proxy on each environment.

Considerations before enabling mod\_proxy
-----------------------------------------

Before you enable mod\_proxy:

*   Understand that using mod\_proxy introduces a dependency on downstream systems that are external to Acquia. Such systems are outside the scope of Acquia's support or advice.
*   Know that dependency on any external service can negatively impact your Acquia-hosted sites.
*   Know that a proxy consumes threads from the allotted connections in Apache. Therefore, the available Apache pool might be overwhelmed when the web service that is proxied to is slow or unavailable.

Acquia recommends that you review and accept these risks and consider other solutions.

Enabling or disabling mod\_proxy
--------------------------------

By default, Apache mod\_proxy settings are disabled on all environments.

To enable or disable mod\_proxy on an environment:

1.  From your Cloud Platform account, go to the environment on which you want to enable or disable mod\_proxy.
2.  Click **Configuration**.
3.  Click the **Proxy** tab.
4.  Do one of the following based on your requirement:
    *   To enable mod\_proxy, set the **Apache mod\_proxy settings** toggle to _On_.
        
        ![cloud-platform_enabling-mod-proxy.png](https://acquia.widen.net/content/d7e0d721-4e73-4438-ac20-eeb5606475e7/web/cloud-platform_enabling-mod-proxy.png)
        
    *   To disable mod\_proxy, set the **Apache mod\_proxy settings** toggle to _Off_.
        
        ![cloud-platform_disabling-mod-proxy.png](https://acquia.widen.net/content/c54066ab-93a2-4694-b12f-c34d78f386ad/web/cloud-platform_disabling-mod-proxy.png)
        

*   Note
    
    *   When you enable or disable mod\_proxy, the system creates a task in the Cloud Platform user interface. However, there is no log.
    *   To ensure enhanced security for your application, Acquia does not enable mod\_proxy by default.