Contact Us 1-800-596-4880

Deploy Applications to CloudHub

Standard Support for Mule 4.1 ended on November 2, 2020, and this version of Mule reached its End of Life on November 2, 2022, when Extended Support ended.

Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted.

MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements.

In addition to using Anypoint Studio, Anypoint Runtime Manager, or the Anypoint Platform CLI to deploy applications to CloudHub, you can also deploy, redeploy, or undeploy applications by using the Mule Maven plugin. To do so, you must meet certain prerequisites, and configure your CloudHub deployment strategy in your project’s pom.xml file.


Before you can deploy to CloudHub using the Mule Maven plugin, you must complete the following tasks:

  • Add the Mule Maven plugin to your project

  • If you are using the HTTP Listener as source for your flow, you need to set its host to and its port to ${http.port}

  • Declare all external classes and resources in the exportedPackages and exportedResources fields on the mule-artifact.json file

Configure the CloudHub Deployment Strategy

Configure the CloudHub deployment strategy in your project’s pom.xml file so you can deploy, redeploy and undeploy your Mule application using the Mule Maven plugin.

Inside the plugin element in your project’s pom.xml file, configure your CloudHub deployment, replacing the placeholder values with your CloudHub information:


Deploy to CloudHub

From the command line in your project’s folder, package the app and execute the deploy goal:

mvn clean package deploy -DmuleDeploy

Redeploy to CloudHub

To redeploy a Mule application using Mule Maven plugin, run mvn clean package deploy -DmuleDeploy as you did to previously deploy the app. CloudHub rewrites the app you had deployed.

Undeploy from CloudHub

To undeploy a Mule application using Mule Maven plugin, run the following command:

mvn mule:undeploy

The undeploy command also deletes the app in Mule Maven plugin 3.3.0 and later versions.

Authentication Methods

When you deploy applications using Mule Maven plugin, you can use different methods to provide your credentials to authenticate against the deployment platform. Depending on the authentication method you use, the parameters to set in the deployment configuration differ:

Authentication Method Description Configuration Parameters

Username and password

Use a CloudHub username and password to authenticate.

  • username

  • password


Use credentials stored in a Maven server, configured inside the Maven settings.xml file.

  • server

Authorization Token

Use an authorization token to access the platform.
See Identity Management for a list of supported single sign-on (SSO) types.

  • authToken

Connected Apps

Use a Connected App to perform the authentication programmatically by communicating with Anypoint Platform.
Note that the Connected App credentials must have the Design Center Developer access scope.
See Connected Apps for Developers for instructions about creating Connected Apps.

  • connectedAppClientId

  • connectedAppClientSecret

  • connectedAppGrantType

For a detailed description of the configuration parameters, see the CloudHub Deployment Reference.

CloudHub Deployment Reference

The following table shows the available parameters to configure the CloudHub deployment strategy in your project’s pom.xml file.

Parameter Description Required


Top-level element



Your Anypoint Platform URI
If not set, by default this value is set to



The version of Mule that you want to run in your CloudHub instance
Ensure that this value is equal to or later than the earliest required Mule version of your application.



Your CloudHub username

Only when using Anypoint Platform credentials to login.


Your CloudHub password

Only when using Anypoint Platform credentials to login.


The name of your application in CloudHub
This name is part of the domain of your deployed app. For example, naming your application application-1 makes your app’s public domain



The absolute path of the JAR file to be deployed
If not set, the path defaults to the location of the JAR file generated at the package phase.



The CloudHub environment to which you want to deploy
This value must match any environment configured in your CloudHub account.




Top-Level element
If you need to set properties for the Mule application you are deploying, you can use the <properties> top-level element:


For example:




The number of workers
By default, this value is 1.



Size of each worker; one of the following values:

  • MICRO (default; 0.1 vCores)

  • SMALL (0.2 vCores)

  • MEDIUM (1 vCore )

  • LARGE (2 vCores)

  • XLARGE (4 vCores)

  • XXLARGE (8 vCores)

  • 4XLARGE (16 vCores)



Region of worker clouds; one of the following values:

  • us-east-1 (default; US East, N. Virginia)

  • us-east-2 (US East, Ohio)

  • us-west-1 (US West, N. California)

  • us-west-2 (US West, Oregon)

  • eu-central-1 (EU, Frankfurt)

  • eu-west-1 (EU, Ireland)

  • eu-west-2 (EU, London)

  • ap-southeast-1 (Asia Pacific, Singapore)

  • ap-southeast-2 (Asia Pacific, Sydney)

  • ap-northeast-1 (Asia Pacific, Tokyo)

  • ca-central-1 (Canada, Central)

  • sa-east-1 (South America, São Paulo)



Enables Object Store V2
By default, it is set to false.



Enables persistent queues
By default, it is set to false.



The Business group path of the deployment
Specify the full hierarchical path from the parent organization to the target Business group, for example:


This value is omitted if businessGroupId is set. If businessGroup and businessGroupId are not set, the value defaults to the main business group of the user.



The Business group ID of the deployment
Instead of specifying the Business group path, you can specify the Business group ID to deploy your application. If businessGroupId and businessGroup are not set, the value defaults to the main business group of the user.
The Business group ID is a mandatory parameter when you have access only to a specific Business group but not to the parent organization.
This parameter is available in plugin version 3.2.7 and later.



The allowed elapsed time, in milliseconds, between the start of the deployment process and the confirmation that the artifact has been deployed

The default value is 1000000.



Maven server with Anypoint Platform credentials
This is only needed if you want to use your credentials stored in your Maven settings.xml file. This is not the Mule server name.



When set to true, skips the plugin deployment goal.
Its default value is false.



When set to true, skips the status verification of your deployed app.
Its default value is false.



Specifies the authorization token to access the platform. You can use this authentication method instead of setting username and password.
See Identity Management for a list of supported single sign-on (SSO) types.

Only when using an Authorization token to login.


Specifies the Connected App clientID value.

Only when using Connected Apps credentials to login.


Specifies the Connected App secret key.

Only when using Connected Apps credentials to login.


Specifies the only supported connection type: client_credentials.

Only when using Connected Apps credentials to login.

Encrypt Credentials

To use encrypted credentials when deploying, you need to set up your Maven master encrypted password and your settings-security.xml file.

  1. Create a master password for your Maven configuration.

    mvn --encrypt-master-password <yourMasterPassword>

    Maven returns your master password encrypted:

  2. Create a settings-security.xml file in your ~/.m2 repository and add your encrypted master password:

  3. Encrypt your Anypoint platform password:

    mvn --encrypt-password <yourAnypointPlatformPassword>

    Maven returns your Anypoint platform password encrypted:

  4. Add your encrypted Anypoint Platform password to your settings.xml file in the <server> section:

  5. In your configuration deployment, reference the credentials injecting the server ID configured in your settings.xml file:

    Make sure that the username and password are not set in the deployment configuration, or they will overwrite the defined server ID.