Deploying API Proxies to Runtime Fabric | MuleSoft Documentation
# Deploying API Proxies to Runtime Fabric
Anypoint Runtime Fabric enables you to deploy API proxies to a Mule runtime.
## Before you Begin
To deploy API proxies to a Mule runtime, you must have the following permissions on your account:
  * Manage APIs Configuration permission
  * Deploy API Proxies permission


You must ensure that you are using API Gateway version 3.8.7, 3.9.1, or 4.1.2.
If you are deploying your API to a Mule 4 environment and want to enable the proxy to support HTTPS requests, first refer to build HTTPS API proxies.
By default, the resources allocated to the proxy app are:
  * CPU: 0.2 vCores
  * Memory: 1.024 GB


You can update resource allocation settings on the application’s **Settings** page in Runtime Manager.
## Deploy an API Proxy
Use API Manager to deploy proxies to Runtime Fabric. You can enable proxies to support inbound and outbound requests over HTTP or HTTPS.
If you need your proxy to support HTTPS, see Build HTTPS API Proxies in the API Manager documentation for additional requirements before getting started.
  1. From Anypoint Platform, select **API Manager** > **Manage API** > **Manage API From Exchange**.
  2. In **API Name** , search for the name of the asset saved in Exchange.
The **Asset type** , **API version** , and **Asset version** fields for the API are auto-populated from Exchange.
  3. For **Managing type** , select **Endpoint with proxy**.
  4. For **Proxy deployment target** , select Runtime Fabric.
  5. Select the Mule version.
  6. For **Implementation URI** , specify the base URL path to access the proxy.
  7. Optionally, specify a **Path**.
  8. If you want to enable SSL for inbound traffic:
    1. Select **HTTPS** for the **Scheme**.
You should now see the **TLS Context for Inbound Traffic** field enabled.
    2. Select **Add TLS Context**.
    3. Select the secret group where you hosted your TLS context from the **Secret group** drop-down.
    4. Select your TLS context for your HTTPS API Proxy from the **TLS Context** drop-down.
  9. Enter the **Port** number for your API proxy.
  10. Select your **Client Provider**.
  11. Click **Advanced Options**.
  12. In **Proxy Version** , select **latest**.
This value ensures that your API proxy uses the latest released proxy version.
  13. Click **Add TLS Context** for **TLS Context for Outbound traffic**.
    1. Select the secret group where you hosted your TLS Context from the **Secret Group** drop-down list.
    2. Select your TLS Context for your HTTPS API Proxy from the **TLS Context** drop-down.
  14. Click **Save**.
Your configuration information is saved and API Manager displays the **Deployment Configuration** section.
  15. In the **Deployment Configuration** section, configure the following:
    1. Select the **Runtime Fabric target**.
    2. Select the **Runtime version**.
    3. Enter the name of the proxy application.


API Manager deploys the API proxy to Runtime Fabric. While deploying, a deployment status dialog appears that indicates:
  1. **Deploying proxy**.
  2. **Starting application**.
  3. **Deploy successful**.


After deployment, you can manage the deployed API proxy from Runtime Manager.
## Enable an HTTPS Proxy Using Anypoint Studio
You can enable the proxy to support HTTPs requests using Anypoint Studio.
  1. Download the API gateway and deploy from API Manager using the instructions in Downloading an API Proxy.
  2. Open the gateway in Anypoint Studio and insert a keystore (SSL cert) using the instructions in Use Anypoint Studio to Configure TLS.
  3. Export and deploy the gateway using Runtime Manager according to the instructions in Deploy a Mule Application to Runtime Fabric.
  4. Enable last-mile security on the application using the instructions in How to enable last-mile security in Runtime Fabric (RTF).


## Related Resources
  * Deploy a Mule Application to Runtime Fabric