Skip to content

Create a Dedicated Deployment

EMQX Dedicated Plan offers independent MQTT service clusters with higher connection and Transactions Per Second (TPS) limits. It also supports more advanced features and complex network architectures. This guide uses the Dedicated Plan as an example to walk you through the steps of creating and utilizing the EMQX Platform.

Create a Deployment

  1. Log in to the EMQX Platform console.

  2. To initiate a new deployment for your project, navigate to either the Console's homepage or the Deployment List page. Here, click + New Deployment.

  3. Select the Dedicated tab.


  4. Configure the specifications according to your needs.

    • Cloud Provider & Region: See Cloud Service Providers and Regions for support.
    • Tier: Select the specification from the drop-down box. Each specification limits a different maximum number of connections and TPS. If your requirements are not met, you can contact us.
    • Billing Method: You can select Hourly billing (to pay by the hour) or Annual prepaid (an annual billing plan).
    • Deployment Name & Project: Provide a name for your deployment and select the appropriate project.
  5. Confirm the deployment information in the Summary area, and then click the Deploy button. This stage will prompt you to review and accept the EMQX Platform Services Agreement. It's important to thoroughly read the agreement and accept its terms to proceed.

  6. Upon accepting the terms, the deployment will begin. Once the deployment status changes to Running, your deployment is successfully created and ready for use.

View Deployment Information

After the deployment is created, it will appear on the EMQX Platform console home page. Click the Dedicated deployment card to enter the deployment overview page. On the overview page, you can check the real-time status and connection information for your deployment.


Basic Information

  • Instance Status: Running status and duration of operation.
  • Sessions: Current and maximum connection counts.
  • Pub&Sub TPS: Current messages sent and received per second, as well as the TPS limit.
  • Traffic: Usage information for the deployed traffic, including monthly usage and free quota.

Connection Information

  • Address: The IP address
  • Ports: 1883 (mqtt) and 8083 (ws) are enabled by default. You can configure TLS/SSL to enable 8883 (mqtts) and 8084 (wss) ports.

Check out the Connection guide to learn more.

Dedicated Deployment Features

To explore the advanced features of the Dedicated Plan, refer to the following links to the specific sections.


Provides REST APIs for integration with external systems, such as querying client information, publishing messages, and creating rules.

Configure TLS/SSL

EMQX Dedicated deployment provides custom one-way/two-way TLS/SSL configuration and supports self-signed and CA-signed certificates.

VPC Peering Connections

VPC peering connection is a network connection between two VPCs. Through this connection, the instances in different VPCs can communicate with each other as if they are in the same network.

PrivateLink enables the proprietary network VPC where the EMQX Platform deployment is located to establish a secure and stable private connection to services on the public cloud. It simplifies the network architecture, enables private access to services, and avoids the potential security risks associated with accessing services over the public network.

Internal Load Balancers

Intranet load balancing is a service that distributes traffic on demand in the internal network, extending the throughput capacity of applications by distributing traffic to different back-end servers, and eliminating single points of failure in the system to improve the availability of applications.

NAT Gateway

NAT gateways can provide network address translation services to provide Dedicated deployments with the ability to access public network resources without the need for VPC peering connections.

Connect to the Deployment

You can use any MQTT client tool to connect to the deployment for testing. It is recommended to use MQTTX to connect to the deployment.