How to Deploy EMQX Enterprise on Google Cloud
Table of Contents
Google Cloud IoT Core will be retired on August 16, 2023. As this date approaches, many users are looking for new solutions for their existing IoT businesses, and EMQX Enterprise is an ideal choice to achieve this goal.
EMQX Enterprise is a large-scale distributed MQTT messaging platform that can be deployed on the Google Cloud Platform (GCP) in multiple ways. You can easily and quickly migrate your devices on IoT Core to EMQX Enterprise and then continue to integrate with your data services in GCP, without affecting the existing business.
To migrate your business from IoT Core to EMQX Enterprise, you basically have three steps to go:
Create an EMQX cluster on GCP.
Connect your devices to EMQX cluster.
Integrate your data with GCP Pub/Sub.
To start with, this article will guide you through the process of deploying EMQX Enterprise on GCP and then test the publishing and subscription of the migrated services.
Create a Virtual Machine Instance on GCP
Before deploying EMQX enterprise, let’s first create a Virtual Machine on GCP.
GCP Virtual Machine Instances allow users to easily deploy and manage applications without creating and managing servers locally.
Here are the steps for creating a VM instance on GCP. You can also refer to the Create and start a VM instance guide.
Log in to the GCP console and click Create a VM.
If you have not created a VM instance before, you will be redirected to the Compute Engine API page. Click ENABLE to enable the Compute Engine API and continue with the creation process.
Check the New VM instance option to start the instance configuration
Choose an appropriate region and zone and machine configuration. In Machine configuration, select
E2for Series and
Customfor Machine type, and allocate 2 vCPUs and 4GB of memory. With this specification, a single EMQX node can handle up to 10,000 MQTT connections and a maximum of 5,000 TPS of concurrent messages.
You can use the EMQX Server Estimate calculator to calculate the recommended hardware specification under various maximum connections and message throughputs.
In the Boot disk configuration, select the Ubuntu 20.04 LTS operating system and change the disk size to 30GB.
Keep the rest of the configurations as default, and click CREATE to start the creating process.
Install EMQX Enterprise
We will deploy EMQX Enterprise with the SSH tool from GCP. Before that, we need to get the download address and installation command from the EMQX website.
In this example, we will deploy EMQX 4.4.16 on Ubuntu 20.04, with an amd64 CPU architecture. You can go to the page Download EMQX Enterprise to get the required information.
Log in to the GCP console and click Navigation menu → PRODUCTS → COMPUTE → Compute Engine → VM Instances to enter the list of VM instances.
Find the VM instance you created and you will see that GCP has assigned a unique external IP address to it. Click on SSH to open your SSH terminal.
In the SSH terminal, enter the root directory and follow the installation commands provided on the download page.
To enter the root directory, you can use the following command:
sudo su cd ../../
Download EMQX Enterprise using the
Install EMQX Enterprise:
sudo apt install ./emqx-ee-4.4.16-otp22.214.171.124-1-ubuntu20.04-amd64.deb
Start EMQX Enterprise:
sudo systemctl start emqx
Congratulations! You have completed the installation of EMQX Enterprise on the GCP VM instance.
Opening Firewall Ports on GCP
After you have installed the service or application on GCP, you need to manually open the required ports to access it from outside. Follow these steps to open the required ports on GCP.
Log in to the GCP console and click Navigation menu → PRODUCTS → VPC network → Firewall to enter the Firewall page.
Click CREATE FIREWALL RULE.
Fill in the following fields to create a firewall rule:
- Name: Enter a name for the rule.
- Network: Select default.
- Priority: Enter a priority number. The lower the number, the higher the priority. Enter 1000 here.
- Direction of traffic: Select Ingress, which means receiving data on specific ports.
- Action on match: Select Allow to allow traffic to pass through.
- Targets: Select All instances in the network to apply the rule to all instances in the network.
- Source filter: Choose the source filter as IPv4 ranges if you want to receive data from all networks or users.
- Source IPv4 ranges: IP address 0.0.0.0/0 means that anyone can send data. You can also configure rules to receive data from specific IP addresses.
- Protocols and ports: If you want to open all ports, select Allow all. Otherwise, open the specified TCP ports. You can open multiple ports simultaneously by separating them with commas. Here, enter 1883, 8883, 8083, 8084, 18083, and 8081.
Click CREATE to create the firewall rule. You will see the rule you created in the list.
Quick Test with MQTTX Client
Now you have completed the installation of EMQX Enterprise on GCP and opened all the required ports. Here are the connection details:
Please replace it with your actual VM Instance public IP address.
|WebSocket SSL/TLS Port||8084|
|REST API Port||8081|
We will use MQTTX to simulate the access of IoT MQTT devices and quickly test whether the server is available.
MQTTX is a cross-platform MQTT 5.0 client tool open-sourced by EMQ. It supports macOS, Linux, and Windows, has rich features, and allows you to easily test MQTT/TCP, MQTT/TLS, and MQTT/WebSocket connections through MQTTX's one-click connection method and graphical interface.
MQTTX Web is the browser version of MQTTX, which eliminates the need for downloading and installation. You can quickly connect to the MQTT server via WebSocket by simply opening the browser.
Access the MQTTX Web page and click New Connection or the + icon on the menu bar to create a connection.
To configure and establish an MQTT connection, you only need to configure:
- Name: Connection name, such as GCP EMQX Enterprise.
- Select the connection type as ws://, as MQTTX Web only supports WebSocket protocol. If you want to test SSL/TLS authentication connections, please download the MQTTX client
- Enter the VM instance public IP address.
- Port: 8083, which is the port corresponding to the WebSockets protocol.
Leave other options at their default settings. You can keep the default settings for the rest fields or set as per your business needs. The corresponding configuration instructions can be found in the MQTTX Manual - Quick Connect.
After configuration, click Connect in the upper right corner of the page to establish the connection.
Subscribe to a topic and publish a message to complete the message publish/subscribe test.
- Click New Subscription, enter testtopic/1 in the pop-up box, and subscribe to it.
- Enter testtopic/1 as the topic in the message-sending box, and use default values for other fields.
- Click the send button at the lower right corner of the Payload input box, and the message will be successfully sent in the chat window.
- Almost simultaneously, a new message will be received in the chat window, indicating that the publish/subscribe test has been completed.
After completing device connection and message publish/subscribe testing, you can also open the EMQX Dashboard in your browser by visiting
http://<ip>:18083and logging in with the default credentials: username admin and password public.
On the Dashboard, you can easily manage and monitor EMQX, manage the device list, and configure various functions such as security and data integration.
Now we have learned how to deploy EMQX Enterprise on GCP. To use EMQX Enterprise in production, we suggest you continue to create an EMQX cluster through the VPC network for better scalability and availability.
In addition to manual installation, you can also deploy EMQX Enterprise on GCP through EMQX Kubernetes Operator and EMQX Terraform. We also highly recommend the fully managed MQTT message cloud service EMQX Cloud.
In the following blogs, we will introduce how to migrate devices from GCP IoT Core to EMQX Enterprise, and how to seamlessly migrate IoT Core services through the GCP Pub/Sub integration of EMQX Enterprise.
Other Articles in This Series
- 3-Step Guide for IoT Core Migration 02 | Migrating Devices from GCP IoT Core to EMQX Enterprise
- 3-Step Guide for IoT Core Migration 03 | Ingesting IoT Data From EMQX Enterprise to GCP Pub/Sub