# Create a Dedicated Deployment
EMQX Cloud's Dedicated Plan offers independent MQTT service instances/clusters with higher connection and TPS limits, as well as greater scalability. This guide will use the Dedicated Plan (Professional) as an example to walk you through the steps of creating and utilizing EMQX Cloud.
# Create a Deployment
Log in to EMQX Cloud Console (opens new window).
You can create a new deployment for a specific project from either the Console homepage or the deployment list page. Click + New.
Click Create Now on the Dedicated tab.
Choose the appropriate specifications and configurations based on your needs.
Plan: Choose the product plan.
Choose Cloud Platform: You can choose from AWS, Azure, or Google Cloud.
Choose Region: Choose the region to deploy EMQX Cloud. To deploy your EMQX Cloud in a different region, you can submit a request via a ticket or email to email@example.com.
Choose Specification: Each specification has different limits on the maximum number of connections and transactions per second (TPS), which can be upgraded or downgraded in later stages.
Billing Method: Choose between Hourly billing or Annual prepaid (with a 15% of discount).
Double-check your setting in the New Deployment tab, and click Deploy.
As part of the deployment process, you'll be asked to agree to the EMQX Cloud Services Agreement, please review the agreement carefully and accept it if you agree with its terms.
After agreeing to the agreement, the deployment process will begin and take about 5 minutes to complete. You can monitor the progress on the Projects page, and once the status changes to Running, your deployment has been successfully created and is ready for use.
# Deployment Overview
The deployment overview page provides real-time status and connection information for your deployment.
- 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.
- Deployment name: A customizable name for the deployment.
- Specifications: The current specification of the deployment, including the ability to switch from hourly billing to annual billing.
- Professional Plan: IP
- Standard Plan: Domain name ending with emqx.cloud
- Professional Plan:
8083(ws) are enabled by default. You can configure TLS/SSL to enable 8883 (mqtts) and 8084 (wss) ports.
- Standard Plan:
8084(wss) ports are enabled by default.
- Professional Plan:
Check out the Connection guide to learn more.
To explore the advanced features included in the Dedicated Plan, you can click the links below.
# Configure TLS/SSL
EMQX Cloud Professional Deployment provides custom one-way/two-way TLS/SSL configuration, and support self-signed certificates 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.
# Configure PrivateLink
PrivateLink enables the proprietary network VPC where the EMQX Cloud 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.
# REST API
EMQX Cloud API follows the REST architecture. You can access the functions of EMQX programmatically.
# 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 Professional deployments with the ability to access public network resources without the need for VPC peering connections.