Help Center/ IoT Device Access/ User Guide/ IoTDA Instances/ Overview
Updated on 2026-03-31 GMT+08:00
View PDF
Share

Overview

IoTDA uses instances to implement data and resource isolation. Currently, the platform provides standard instances.

  • Standard Edition

    You can experience all functions of Standard Edition free of charge within the limit on the number of messages and devices per day.

    If you want to increase device and message quotas, modify the configuration on the instance page and select units with desired specifications.

  • Enterprise Edition

    After you purchase a dedicated instance, it runs in your specified Virtual Private Cloud (VPC). You can use independent public and private IP addresses to access the platform. The enterprise edition uses the physical multi-tenant architecture. The resources you purchase are exclusively used, improving resource security and isolation.

Restrictions on Purchasing Instances

Note the following restrictions to prevent purchasing and creation failures:

  • Restrictions on purchasing standard edition instances
    • Each tenant can subscribe to only one free trial instance in the same region.
  • Restrictions on purchasing enterprise edition instances
    • User permissions

      Before purchasing an enterprise edition instance, authorize cloud service access. Purchase is available only after the authorization is successful. For details, see Configuring Cloud Service Access Authorization.

    • Instance quota

      A maximum of five enterprise edition instances can be purchased in a VPC network.

    • Available IP addresses in the subnet

      At least 10 IP addresses shall be available in a subnet.

Early-stage Planning

  • Public/Private network interworking

    Interworking with the public network: Public network IP addresses are provided by the platform. You do not need to plan them.

    Interworking with the private network: When subscribing to IoTDA, specify the VPC and subnet. By default, IoTDA can be accessed only from the specified subnet. Therefore, provide a properly planned subnet when purchasing IoTDA. If the data transfer function of IoTDA is used, for example, if data needs to be forwarded to Kafka, the IoTDA and Kafka services must be in the same VPC.

    For enterprise editions subscribed before December 1, 2025, data can be forwarded only to Kafka in the same subnet.

  • VPC

    Determine the VPC network segment. Currently, the VPC supports three network segments: 10.0.0.0/8–24, 172.16.0.0/12–24, and 192.168.0.0/16–24. For details about the commissioning guide, see Creating a VPC.

    Determine the subnet division. The subnet network segment must be within the VPC network segment.

  • Route table

    Determine the route table. The default route table only ensures that all subnets in the same VPC can communicate with each other. If the routing policy in the default route table cannot meet your requirements, customize a route table. For details, see Route Table Overview.

Configuring Cloud Service Access Authorization

The platform can work with Huawei Cloud services. When you purchase an enterprise instance for the first time, perform access authorization. After the authorization is successful, you can create ports, subnets, and security groups. In addition, you can connect to the VPC Endpoint service so that applications or devices can access the platform through a private network.

  1. Access the IoTDA service page and click Access Console.
  2. In the navigation pane, choose IoTDA Instances. Click Buy Instance and select Enterprise. A dialog box is displayed for you to authorize cloud service access.
  3. On the displayed page, click Agree. After the authorization is successful, an agency named iotda_admin_trust is created in Identity and Access Management (IAM). For details, see Agency Authorization.
Parent topic: IoTDA Instances