--- schema_version: "1" id: 35364676a730e8e4cd82557ab59793052a16368fc91de135a1cf68defbae4148 title: Deploying Agent Network Instances collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/agent-network/latest/af-deploy-agent-network-targets.md canonical_url: https://docs.mulesoft.com/agent-network/latest/af-deploy-agent-network-targets source_site: docs.mulesoft.com content_type: documentation content_hash: 2b3c3a78fc6877162f28ad981e86b45fd05f5173d2e6514d1e3b93c6f8b082a3 description: MuleSoft Documentation Site release: "2.0" latest: true --- --- product: Building Agent Networks version: 2.0 is-latest-version: true --- # Deploying Agent Network Instances > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Deploy your agent network instance to a CloudHub 2.0 shared space, a CloudHub 2.0 private space, or to a Runtime Fabric target. Agent network deployments are available on US Cloud and EU Cloud hosts only. For more information, see [Control Plane Hosting Options](https://docs.mulesoft.com/hosting-home/#control-plane-hosting-options). Additionally, agent brokers follow the same monthly patching cadence as CloudHub 2.0. For the update schedule, see [MuleSoft Commercial Cloud Schedule](https://docs.mulesoft.com/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#mulesoft-commercial-cloud-schedule). ## Agent Network Deployments and Omni Gateway When you deploy, Omni Gateway secures inbound traffic to your agent network and outbound traffic from your brokers, agents, and MCP servers. Omni Gateway applies these policies automatically at deployment.
Agent TypePolicy

Broker

  • A2A Agent Card policy

  • Tracing policy

  • Agent Connection Telemetry policy

Agent

(ingress and egress)

  • A2A Agent Card policy

  • Tracing policy

  • Agent Connection Telemetry policy

MCP Server

(ingress and egress)

  • MCP Support policy

  • Tracing policy

  • Agent Connection Telemetry policy

### Last-Mile Security Considerations for Agent Networks Agent networks in version 2.0 don’t support Last-Mile Security for outbound (egress) traffic on the Omni Gateway. If you have enabled Last-Mile Security, the agent network deploys and the broker can answer general questions, but it can’t route requests to downstream agents or MCP servers. Agent networks route outbound traffic through the egress gateway (on port 8082, cluster endpoint). Last-Mile Security enforces TLS on the ingress-gateway-to-pod hop. The outbound path bypasses this hop, so the connections can’t be established. If your deployment requires Last-Mile Security for other applications, deploy your agent network to a separate egress gateway that has Last-Mile Security disabled. The broker’s `egressgw.url` resolving to the cluster endpoint is expected behavior, regardless of the Last-Mile Security setting. ## Before You Begin Make sure you review the [prerequisites for setting up agent network gateways and deployment targets](https://docs.mulesoft.com/agent-network/latest/af-get-started#before-you-begin). > [!IMPORTANT] Redeploying an agent network to a different target or gateway (for example, switching > between a shared space and a private space, or changing to a different gateway) is not supported > and fails with a Runtime Manager error. To deploy to a different target or gateway, first manually > delete the existing Runtime Manager application, then redeploy. When you deploy your agent network, the system deploys one instance for each connection defined in your agent network. If your agent network contains brokers, the system deploys one instance per broker. ## Deploy Your Network Using MuleSoft Vibes Details Use MuleSoft Vibes to deploy your agent network instances. For more information, see [Creating API Specs with MuleSoft Vibes](https://docs.mulesoft.com/anypoint-code-builder/vibes-api-ai-create-spec). 1. In the Anypoint Code Builder activity bar, click the agent icon ![](/mulesoft/current/en-us/agent-network/latest/_images/af-acb-dev-agent-icon.png). 2. Tell the agent that you want to deploy your agent network. MuleSoft Vibes does the rest. To get started, try one of these suggested messages. - Deploy my agent network project to the production environment. - Deploy the hello-world-network project to staging. - Deploy agent network project at /path/to/project to dev environment with specific gateways. - Deploy my agent network to CloudHub 2.0. ## Deploy Your Network Using Anypoint Code Builder Details Deploy your agent network instance to a CloudHub 2.0 space or Runtime Fabric target directly from Anypoint Code Builder. 1. If you’re not logged in already, log in to your Anypoint Platform account. 2. In Anypoint Code Builder, choose one of the following: 3. In Explorer, right-click a project file and select **Deploy Agent Network**. 4. From the Command Palette, run this command: **MuleSoft: Deploy Agent Network**. 5. In Deploy Agent Network, specify the environment, target space, gateways, and other deployment information. If you don’t see any deployment targets to select, then you need to set up your target deployment space and set up gateways. For instructions, see [Get Started with Agent Networks](https://docs.mulesoft.com/agent-network/latest/af-get-started). 6. Select **Deploy**. 7. Your instances are now deployed and ready to test. The system deploys one instance for each connection defined in your agent network. If your agent network contains brokers, the system deploys one instance per broker. Next, discover your agent network assets in **Agents & Tools** in Exchange, view your agent network in Agent Visualizer, apply a governance policy in API Manager, or monitor your agent network activity in Anypoint Monitoring. ## Undeploy Your Network Using MuleSoft Vibes Use MuleSoft Vibes to undeploy your agent network instances. For more information, see [Creating API Specs with MuleSoft Vibes](https://docs.mulesoft.com/anypoint-code-builder/vibes-api-ai-create-spec). 1. In the Anypoint Code Builder activity bar, click the agent icon ![](/mulesoft/current/en-us/agent-network/latest/_images/af-acb-dev-agent-icon.png). 2. Tell MuleSoft Vibes that you want to undeploy your agent network. MuleSoft Vibes does the rest. To get started, try one of these suggested messages. - Undeploy my agent network project from the production environment. - Undeploy the \[project-name\] project from staging. - Undeploy agent network project at /path/to/project from dev environment. ## Undeploy Your Network Using Anypoint Code Builder Details Undeploy your agent network instances directly from Anypoint Code Builder. When you undeploy, all API instances and applications in the agent network are stopped and runtime resources are removed. 1. If you’re not logged in already, log in to your Anypoint Platform account. 2. In Anypoint Code Builder, choose one of the following: 3. In the Explorer view, right-click a project file and select **Undeploy Agent Network**. 4. From the Command Palette, run this command: **MuleSoft: Undeploy Agent Network**. 5. In the confirmation dialog, select **Undeploy**. 6. Anypoint Code Builder removes all deployed runtime resources. For details, check the Agent Fabric CLI output logs. ## Deploy or Undeploy a Network Using the Anypoint CLI Details If you run operations within a CI/CD environment, use Anypoint CLI plugin to set up, create, build, publish, unpublish, deploy, and undeploy agent networks. For more information, see [Build Agent Networks in a CI/CD Environment](https://docs.mulesoft.com/agent-network/latest/af-build-agent-networks-in-a-ci-cd-environment). ## Configure CPU and Memory Resources for an Agent Broker Configure CPU and memory resources for brokers when you deploy an agent network with Anypoint CLI. By default, brokers reserve `20m` of CPU and `700Mi` of memory, with limits of `2000m` CPU and `700Mi` memory. Specify the resource settings in a deployment configuration file or directly in the deploy command. Don’t use both methods in the same command. To specify the settings in a deployment configuration file: 1. Create a `deployment-config.yaml` file with the resource settings: ```yaml brokers: resources.cpu.reserved: 20m resources.cpu.limit: 2000m resources.memory.reserved: 700Mi resources.memory.limit: 700Mi ``` 2. Pass the file to the deploy command with `--deployment-properties-file`: \--deployment-properties-file=/path/to/deployment-config.yaml To specify a resource setting directly in the deploy command, use `--deployment-property` with the broker scope, resource property, and value. For example, to reserve `50m` of CPU: \--deployment-property brokers:resources:cpu:reserved:50m ## Resolve Agent Network Deployment Errors in Anypoint Code Builder If you try to deploy an agent network project and see errors related to CLI version, install the latest Anypoint Code Builder version (1.24.1 or later) and then rebuild, republish, and deploy your project. If you try to deploy an agent network project and see errors related to invalid API metadata, use API Manager to delete existing API instances that were created with previous a Anypoint Code Builder version. Then rebuild, republish, and deploy your project. ## See Also - [Agent Network 2.0 Project File Reference](https://docs.mulesoft.com/agent-network/latest/af-project-files) - [Agent Fabric Overview](https://docs.mulesoft.com/general/agent-fabric-overview) - [Managed Omni Gateway in Shared Spaces with Unified Traffic Control](https://blogs.mulesoft.com/news/managed-omni-gateway-in-shared-spaces-with-unified-traffic-control/) [Troubleshoot Agent Networks](https://docs.mulesoft.com/agent-network/latest/af-troubleshoot-agent-networks)