EMQX Platform Docs

English

简体中文

English

简体中文

Appearance

Contact Us

Create a Premium Deployment ​

The EMQX Premium Plan offers a robust EMQX Cluster with advanced features for large-scale, mission-critical applications. This guide provides instructions on how to create a Premium deployment on the EMQX Platform.

Apply for a Trial ​

EMQX Premium deployments can only be created by requesting a trial. Users cannot create them independently. You can contact us to request a trial period. Each user can create two trial Premium deployments during the trial period. If both deployments are deleted during the trial period, you cannot request the trial again. The trial period is free of charge, and you can enjoy all the features of the Premium Plan.

  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. In Choose Plan, select Premium.

  4. Click Contact Us at the bottom and you will be lead to the Contact Sales page where you can submit your trial application.

    apply_premium_trial

If your trial request is approved, you will receive an email with details about the trial period, deployment platform, and region, as well as the activation time.

Create a Deployment ​

When your trial is activated, you can go to the Platform Console to deploy your Premium Plan.

  1. Under the Cloud Provider & Region, select a deployment region.

  2. Under the Deployment Name & Project, provide a name for your deployment and select the appropriate project.

  3. 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.

    deploy_premium

  4. 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 Premium 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.

premium

Basic Information ​

  • Instance Status: Running status and deployment creation time.
  • Sessions: Current and maximum connection counts.
  • Pub&Sub TPS: Current messages sent and received per second, as well as the TPS limit.
  • Traffic: Traffic usage information for the deployment, including all public network traffic that flows in and out of your deployment.
  • Storage: The storage space can be used for Durable Sessions and Event History.

Connection Information ​

  • Address: The IP address.
  • Ports: 1883 (mqtt), 8083 (ws), 8883 (mqtts), and 8084 (wss) ports are enabled by default.
  • Ports Management: Allows you to disable or enable an individual port separately.

Check out the Connection Guide to learn more.

Premium Deployment Features ​

The Premium Plan provides you with the following the advanced features.

Deployment API ​

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

Configure TLS/SSL ​

The EMQX Premium 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 Premium deployments with the ability to access public network resources without the need for VPC peering connections.

Dedicated Storage Layer ​

The Premium Plan provides a dedicated storage layer for each deployment, providing isolated and secure data storage. Data is stored across multiple availability zones for high availability, with automatic backups and easy restoration options, ensuring maximum reliability and data protection.

Durable Sessions ​

Durable Session allows the EMQX Platform to persist client sessions to the built-in database instead of memory. Client session data is retained even after the server restarts, ensuring uninterrupted connectivity.

Event History ​

The Event History service enables the EMQX Platform to record the client and message events for further monitoring and analysis.

Cluster Linking ​

The Cluster Linking feature facilitates client communication and message transmission between geographically distributed Premium deployments.

Connect to the Deployment ​

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

Convert to a Commercial Deployment ​

At the end of the trial period, your trial deployment will be automatically stopped. If you wish to continue using the Premium deployment, please reach out to our Sales team to purchase the Premium Plan service. For detailed pricing information, refer to Pricing - Premium Plan.

TIP

Users cannot convert a trial deployment to an annual subscription directly through the Platform Console. To make this conversion, please contact our Sales team, who will assist with the process in the backend.