IoT Platform:Manage instance endpoints

Background

• Endpoint types

  • Endpoints are categorized into public endpoints and VPC endpoints. VPC endpoints reduce network latency and public bandwidth costs while improving connection security and stability.

  • Devices can connect to IoT Platform over MQTT, CoAP, or HTTP. Premium Enterprise Edition instances also support VPC connections, allowing devices to use the MQTT VPC endpoint.

  • To access IoT Platform from an ECS instance within a VPC, configure VPC endpoints for AMQP server-side subscriptions and IoT Platform API calls.

• Instance types

  • Standard and Premium Enterprise Edition instances in China (Shanghai), China (Beijing), and China (Shenzhen) support binding a fixed IP to the MQTT endpoint.

  • Premium Enterprise Edition instances require manual creation of a dedicated MQTT endpoint. You can also customize the port number and certificate.

View endpoints for legacy public instances

Replace the following parameters in the endpoint URLs.

View endpoints for public and Enterprise Edition instances

1. Log on to the IoT Platform console. In the upper-left corner of the page, select the region where your instance is located.

2. On the Overview page, click the instance alias or ID.

3. In the upper-right corner of the Instance Details page, click View Development Configurations.

4. In the Development Configurations panel, click the MQTT, CoAP, AMQP, or other protocol tabs to view the endpoint information. Click Copy next to the domain name to copy the endpoint address. Click the help icon to view the port. For port details, see View endpoints for legacy public instances.

   Important

   • For Premium Enterprise Edition instances, you must create the MQTT endpoint manually. Create a dedicated MQTT endpoint for a Premium Enterprise Edition instance.

   • For device connections over HTTPS, only the unique-certificate-per-device and pre-registration-based unique-certificate-per-product methods are supported. These methods use different endpoints:

     • If you use the unique-certificate-per-device method, the endpoint is displayed on the HTTP tab.

     • The pre-registration-based unique-certificate-per-product method is supported only in the China (Shanghai) region. The endpoint is iot-auth.cn-shanghai.aliyuncs.com.

   • If you have enabled ID² authentication for your Enterprise Edition instance, the ID² Authentication Address on the Manage ID² tab of the Development Configurations panel is not displayed. For the address format, see View endpoints for legacy public instances.

   The Development Configurations panel has two sections: Public Endpoint and VPC Network Endpoint. Each section contains tabs for supported protocols (MQTT, CoAP, HTTP, AMQP). On these tabs, you can find endpoint addresses, connection ports, and related settings. For example, the MQTT tab shows the endpoint address, connection port, and the Fixed IP binding status.

Bind a fixed IP to an endpoint

A fixed IP ensures that DNS resolution remains stable when IoT Platform scales its IP addresses. If you use IoT SIM cards with data plans restricted to specific IP addresses and your carrier does not support domain name configuration, add the fixed IP to the carrier's IP allowlist.

To bind a fixed IP to the public MQTT endpoint of an instance:

• For public instances, you can assign two fixed IPs for MQTT connections.

  1. In the upper-right corner of the Instance Details page of the public instance, click View Development Configurations.

  2. In the Development Configurations panel, on the MQTT tab, click Set next to Fixed IP.

  3. In the dialog box that appears, click OK to obtain two fixed IPs.

  If the fixed IPs are no longer needed for MQTT connections, click Unbind.

• For Premium Enterprise Edition instances, a fixed IP is automatically assigned when you manually create a public MQTT endpoint. Unbinding is not supported.

Create a dedicated MQTT endpoint for Premium Enterprise Edition instances

To create an MQTT endpoint for a Premium Enterprise Edition instance:

1. In the upper-right corner of the Instance Details page of the Premium Enterprise Edition instance, click View Development Configurations.

2. In the Development Configurations panel, on the MQTT tab, click Create.

3. In the Create Endpoint dialog box, configure the endpoint information.

   Parameter	Description
   Custom port	The port number for MQTT connections. The default port is 1883.
   Enable VPC	Yes: Enables VPC connections. Configure the VPC, vSwitch Zone, vSwitch, and security group. This creates both public and VPC MQTT endpoints. Important To enable an MQTT endpoint over a VPC, activate the PrivateLink service. If PrivateLink is not activated, click Enable to go to the VPC console and activate it. No (Default): Disables VPC connections. This creates only a public MQTT endpoint. Important If you select No, you cannot enable VPC connections for this endpoint later.
   Authorization	If you enable VPC connections, grant authorization. Click Authorize. The system creates a role and authorization policy to allow devices to connect to IoT Platform over the VPC. Service-linked roles.
   VPC	After you enable VPC connections and grant authorization, configure these parameters. Select an existing VPC and vSwitch. You can click Create VPC or Create vSwitch to create new ones. Create a VPC and Create a vSwitch.
   vSwitch zone
   vSwitch
   Security group	After you enable VPC connections and grant authorization, configure this parameter. Select an existing security group. You can click Create Security Group to create one. Create a security group.

4. Click OK.

   After the endpoint is created, the new endpoint appears under MQTT Device Connection.

Customize the MQTT certificate for Premium Enterprise Edition instances

To customize the certificate and domain name for MQTT connections to a Premium Enterprise Edition instance:

1. In the upper-right corner of the Instance Details page of the Premium Enterprise Edition instance, click View Development Configurations.

2. In the Development Configurations panel, on the MQTT tab, click Configure under Custom Certificate.

3. In the Custom Certificate dialog box, for Custom Configuration, click On.

   Note

   If Custom Configuration is already enabled, skip this step.

4. Enter the PEM-formatted certificate content and private key obtained from your certificate authority (CA), then click OK.

   Warning

   Updating the certificate content or private key after initial configuration may cause certificate verification to fail, which disconnects devices from IoT Platform and interrupts services. Proceed with caution.

   The page displays the custom domain name parsed from your certificate. Use this domain name for MQTT device connections.

   Important

   Configure a CNAME record with your domain provider to resolve the custom domain name to the instance's default MQTT endpoint.