--- schema_version: "1" id: a6f8d02807cb00ed556ff8fc865dd1e782ca3d2ad9b5b87b6c8d92ecff0ac438 title: Deploying AS2, HTTP, and HTTPS Receive Endpoints collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/deploying-receive-endpoints.md canonical_url: https://docs.mulesoft.com/partner-manager/latest/deploying-receive-endpoints source_site: docs.mulesoft.com content_type: documentation content_hash: fd64a96ddf635731475aa3fac33e02ec728ddc0f116cf31161b79f492f0fee60 description: MuleSoft Documentation Site release: 2.x latest: true --- --- product: Partner Manager version: 2.x is-latest-version: true --- # Deploying AS2, HTTP, and HTTPS Receive Endpoints > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can deploy AS2 receive, HTTP receive, and HTTPS receive endpoints on a public or private port. ## Deploy to CloudHub 1.0 on a Public Port When an AS2 or HTTPS receive endpoint is deployed to CloudHub with the private port configuration disabled, the endpoint application is deployed on the public HTTPS port (`8082`) or HTTP port (`8081`), with the traffic routed through the [shared load balancer](https://docs.mulesoft.com/cloudhub/dedicated-load-balancer-tutorial). The value in the URL field is automatically generated when you deploy a message flow that uses this endpoint. You can view the runtime application name and external URL for a deployed endpoint from the endpoint details page. For example: ![Example of a runtime application name and external URL](/mulesoft/current/en-us/partner-manager/latest/_images/pm-receive-endpoint-url.png) You can share the external URL with the partners that send AS2, HTTP, or HTTPS messages to this endpoint. If your organization uses Anypoint Virtual Private Cloud without a dedicated load balancer (DLB), your organization’s platform administrator can configure the necessary [Anypoint VPC firewall rules](https://docs.mulesoft.com/cloudhub/vpc-firewall-rules-concept) to allow specific partner or third-party connection IP addresses to access the endpoint. ## Deploy to CloudHub 1.0 on a Private Port To deploy an AS2, HTTP, or HTTPS receive endpoint to CloudHub 1.0 with the private port configuration enabled, you can: - Deploy a message flow that includes the receive endpoint. - Set CloudHub to automatically deploy newly created endpoints to a private port, as described in [Configuring CloudHub 1.0 Deployment Settings](https://docs.mulesoft.com/partner-manager/latest/cloudhub-deployment-settings). Endpoints with the private port configuration enabled are deployed to the private HTTPS port `8092` or HTTP (only for AS2) port `8091`. You can view the runtime application name, internal URL, and external URL for a deployed endpoint from the endpoint details page, which you can access from the <\*host\*> page (AS2 endpoints) or partner page (HTTP or HTTPS endpoints), or from a message flow. Once an endpoint is deployed, follow these steps: 1. Configure URL mapping rules to forward the messages received from your partners to an application, as described in the following sections and in [Dedicated Load Balancer Mapping Rules](https://docs.mulesoft.com/cloudhub/lb-mapping-rules). 2. Have your organization’s platform administrator add your partner’s IP addresses to a list of allowed addresses in the DLB setting, as described in [Dedicated Load Balancer Allowlists](https://docs.mulesoft.com/cloudhub/lb-allowlists). ## Deploy to CloudHub 2.0 Partner Manager deploys AS2 and HTTP inbound endpoints on CloudHub 2.0 with a HTTPS listener. - When using a shared space as the deployment target, the endpoints are accessible over the Internet and HTTP requests aren’t allowed. - When using a private space as the deployment target, you can use CloudHub 2.0 networking configurations, such as Ingress and Firewall rules, to manage and route incoming requests to your runtime applications. - If you want to allow HTTP requests to the AS2, HTTP, or HTTPS inbound endpoint application: 1. Use a private space as the deployment target. 2. On the **Advanced** tab, select `Accept HTTP` in the **HTTP requests** field. 3. Optionally, configure Network-Level Ingress Rules to allow HTTP requests from specific IP addresses. - To keep a custom public ingress URL stable across redeployments for AS2 or HTTP inbound endpoints, enable **Preserve Public URL of Ingress application** in the endpoint settings. If this option isn’t enabled, Partner Manager can regenerate the public ingress URL when redeploying the endpoint or message flow. ## External URLs and Mapping Rules for Deployed Receive Endpoints The external URLS for receive endpoints deployed to public or private ports vary depending on the endpoint type, DLB domain, and input start\_paths. You can share external URLs with your partners. ### External URL and Mapping Rules for an AS2 Receive Endpoint The external URL for an AS2 receive endpoint is `https://{DLB-domain}/{Input-path}/receive-as2`. For example, if the name of your DLB domain is `mythical.lb.anypointdns.net` and the runtime application name is `b2b-inbound-as2-zap3`, your administrator can add a URL mapping rule in the DLB settings to forward incoming requests to the runtime application within your Anypoint VPC: ![URL mapping rules for AS2 in the DLB settings](/mulesoft/current/en-us/partner-manager/latest/_images/url-mapping-rules-as2.png) With this configuration, the external AS2 endpoint URL is `https://mythical.lb.anypointdns.net/as2/mythical/receive-as2/`. ### External URL and Mapping Rule for an HTTPS Receive Endpoint The external URL for an HTTPS endpoint is `https://{DLB-domain}/{Input-path}/{base-path}/{message-type}`. For example, if the name of your DLB domain is `mythical.lb.anypointdns.net`, the base path you configured for the endpoint is `send2`, and the runtime application name is `b2b-inbound-http-ognq`, then your administrator can add a URL mapping rule in the DLB settings to forward incoming requests to the runtime application within your Anypoint VPC. For example: ![URL mapping rules for HTTPS in the DLB settings](/mulesoft/current/en-us/partner-manager/latest/_images/url-mapping-rules-https.png) ## Deploy to Runtime Fabric Partner Manager deploys AS2 and HTTP inbound endpoints to Runtime Fabric with an HTTP listener. You can expose HTTPS endpoints for internal and external users by using Runtime Fabric network configurations and Ingress rules. ## See Also - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [AS2 Receive Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-as2-receive) - [HTTP and HTTPS Receive Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-https-receive)