All Products
Search

This Product

    Lindorm:Create an instance

    Document Center

    Lindorm:Create an instance

    Last Updated:Dec 04, 2025

    You can create an instance in the Lindorm console. This topic describes how to create a Lindorm instance and its configuration parameters.

    Prerequisites

    An Alibaba Cloud account is required.

    Precautions

    If your application is deployed on an ECS instance, ensure that the Lindorm instance and the ECS instance meet the following conditions to ensure network connectivity. For more information about how to view ECS instance information, see View instance information.

    • They are in the same region. To achieve lower network latency, we recommend that you place them in the same zone.

    • They use the same network type.

    Note

    A virtual private cloud (VPC) provides higher security. We recommend that you use a VPC. If you use a VPC, ensure that both instances are in the same VPC.

    Procedure

    1. Log on to the Lindorm console.

    2. On the Instances page, click Create.

      Note

      You can also navigate to the product page and click Buy Now to create an instance.

    3. In the Product Type section, select Lindorm, New Editon of Lindorm Available for Purchase, or Lindorm Tunnel Service.

      Note

      For more information about product series, see Product series.

    Lindorm

    1. In the Billing Method section, select Subscription or Pay-as-you-go.

      Note

      You can change the billing method in the console after the instance is created.

      • Subscription: A prepaid billing method where you pay for resources before you use them. This method is ideal for long-term use and is more cost-effective than the pay-as-you-go method. The longer the subscription duration, the greater the discount.

      • Pay-as-you-go: This billing method charges you hourly for the resources that you use. It is suitable for short-term use because you can release an instance at any time to save costs.

    2. Configure the instance parameters.

      Parameter

      Description

      Basic Instance Fee

      Fixed to Lindorm Multimodal Database.

      Deployment Mode

      • Single-zone: The primary and secondary nodes are in the same zone. This mode is suitable for scenarios that require disaster recovery within a single data center.

      • Multi-zone High-availability Edition: The primary and secondary nodes are in different zones. This mode provides cross-zone disaster recovery and supports only LindormTable.

      • Multi-zone Basic Edition: The primary and secondary nodes are in different zones. This mode provides cross-zone disaster recovery and supports all engines.

      Region

      Select the region where the instance resides.

      Note

      • You cannot change the region after the instance is created. Select the region with caution.

      • If your application is deployed on an ECS instance, select the same region as the ECS instance. Otherwise, the instances cannot communicate over the internal network.

      Zone

      Select the zone where the instance resides.

      Note

      If your application is deployed on an ECS instance, we recommend that you select the same zone as the ECS instance to reduce network latency.

      Multi-zone

      This parameter is displayed only when you set Deployment Mode to Multi-zone High-availability Edition or Multi-zone Basic Edition.

      VPC

      Select the VPC where the instance resides. If you do not have a VPC, you can create one in the VPC console. For more information, see Create and manage a VPC.

      vSwitch

      Select the vSwitch to which the instance is connected. If you do not have a vSwitch, you can create one in the VPC console. For more information, see Create a vSwitch.

      Note

      This parameter is not available if you set Deployment Mode to Multi-zone High-availability Edition or Multi-zone Basic Edition.

      Primary Zone

      Select the zones for the instance. The zones for the primary, secondary, and client nodes cannot be the same.

      Note

      This parameter is displayed only when you set Deployment Mode to Multi-zone High-availability Edition or Multi-zone Basic Edition.

      Secondary Zone

      Client Node Zone

      vSwitch for Primary Zone

      Select the vSwitch to which the instance is connected.

      Note

      This parameter is displayed only when you set Deployment Mode to Multi-zone High-availability Edition or Multi-zone Basic Edition.

      vSwitch for Secondary Zone

      vSwitch for Client Node Zone

      Cluster Name

      Set a name for the instance to identify it for your business.

      Storage Type

      The valid values are Standard Cloud Storage, Performance Cloud Storage, Capacity Cloud Storage, Local SSD, and Local HDD. Select a storage class as needed. For more information, see Storage classes.

      • Standard: Suitable for scenarios that require real-time data access, such as feed streams, chats, real-time reports, and online computing.

      • Performance: Suitable for scenarios that require low-latency data access, such as ad bidding, user personas, audience segmentation, real-time search, and risk control.

      • Purchase Capacity Storage: Suitable for scenarios that require Infrequent Access to data, such as monitoring logs, historical orders, audio and video archiving, data lake storage, and offline computing.

      • Local SSD: Local disks are from a single physical server and provide low latency, high random input/output operations per second (IOPS), high throughput, and high cost-effectiveness. This storage class is suitable for online services such as online games, e-commerce, ApsaraVideo Live, and media. It meets the low latency and high I/O performance requirements of I/O-intensive applications for block storage.

      • Big Data: Local disks are from a single physical server and provide low latency, high random IOPS, high throughput, and high cost-effectiveness. This storage class is suitable for industries such as the internet and finance that have big data computing and storage analysis requirements. You can use this storage class for business scenarios that require mass data storage and offline computing.

      Select Engine Type

      Includes LindormTable, LindormTSDB, Search Engine, and Stream Engine. Select the node specifications and number of nodes for the data engines as needed. For more information, see Select engine types and Select node specifications and the number of nodes.

      • LindormTable: Select the Node Spec of Wide Table Engine (HBase/Cassandra APIs) and Wide Table Nodes. The unit is core.

      • LindormTSDB: Select the Node Spec of Time Series Engine (TSDB API) and Time Series Engine Nodes. The unit is core.

      • Search Engine: Select the LindormSearch Node Specification (Solr API/Elasticsearch API) and Search Engine Nodes. The unit is core.

      • Stream Engine: Select the Specifications of Streaming Data Nodes and Number of Streaming Data Nodes. The unit is core.

      Note

      • If you set Storage Type to Local SSD or Big Data, you cannot select node specifications for data engines. You can only select Node Spec of Local Disk and the number of nodes for data engines.

      • If you set Storage Type to Local SSD or Big Data, you cannot select the Stream Engine.

      Storage Space

      Select the storage space for the instance.

      Purchase Capacity Storage

      Specifies whether to enable Capacity Cloud Storage for the instance. For more information, see Capacity Cloud Storage.

      Note

      The actual available storage capacity of cloud storage is the total capacity. Local disk clusters use a triplicate architecture. The actual available storage capacity is one-third of the total capacity.

      Capacity Storage

      Select the capacity of the Capacity Cloud Storage for the instance.

      Note

      This parameter is required only if you set Purchase Capacity Storage to Yes.

      Activate LDPS

      Select whether to enable the compute engine.

      Subscription Length

      If you create a subscription instance, select a subscription duration. You can select a duration of 1 to 9 months or 1 to 3 years.

      Note

      If you want to enable auto-renewal for the instance, select Auto-renewal. Make sure that your account has a sufficient balance before the instance expires.

      Resource Group

      Select a resource group to manage the instance. You can select an existing resource group or create a new one. For more information about how to create a resource group, see Create a resource group.

    New Editon of Lindorm Available for Purchase

    1. In the Payment mode section, select Subscription or Pay-as-you-go.

      Note

      You can change the billing method in the console after the instance is created.

      • Subscription: A prepaid billing method where you pay for resources before you use them. This method is ideal for long-term use and is more cost-effective than the pay-as-you-go method. The longer the subscription duration, the greater the discount.

      • Pay-as-you-go: This billing method charges you hourly for the resources that you use. It is suitable for short-term use because you can release an instance at any time to save costs.

    2. Configure the instance parameters.

      Parameter

      Description

      Deployment Scenario

      • Single-zone Deployment: The primary and secondary nodes are in the same zone. This mode is suitable for scenarios that require disaster recovery within a single data center.

      • Multi-zone High-availability Edition: The primary and secondary nodes are in different zones. This mode provides cross-zone disaster recovery and supports only LindormTable.

      • Multi-zone Basic Edition: The primary and secondary nodes are in different zones. This mode provides cross-zone disaster recovery and supports all engines.

      Instance Name

      Set a name for the instance to identify it for your business.

      Region Type

      Select the region where the instance resides.

      Note

      • You cannot change the region after the instance is created. Select the region with caution.

      • If your application is deployed on an ECS instance, select the same region as the ECS instance. Otherwise, the instances cannot communicate over the internal network.

      Availability Zone

      Select the zone where the instance resides.

      Note

      If your application is deployed on an ECS instance, we recommend that you select the same zone as the ECS instance to reduce network latency.

      VPC

      Select the VPC where the instance resides. If you do not have a VPC, you can create one in the VPC console. For more information, see Create and manage a VPC.

      vSwitch

      Select the vSwitch to which the instance is connected. If you do not have a vSwitch, you can create one in the VPC console. For more information, see Create a vSwitch.

      Note

      This parameter is not available if you set Deployment Mode to Multi-zone High-availability Edition or Multi-zone Basic Edition.

      Primary Zone

      Select the zones for the instance. The zones for the primary, secondary, and client nodes cannot be the same.

      Note

      This parameter is displayed only when you set Deployment Mode to Multi-zone High-availability Edition or Multi-zone Basic Edition.

      Secondary Zone

      Coordinator Node Zone

      Primary AZ Switch

      Select the vSwitch to which the instance is connected.

      Note

      This parameter is displayed only when you set Deployment Mode to Multi-zone High-availability Edition or Multi-zone Basic Edition.

      Standby zone switch

      Coordination Node Availability Zone Switch

      Storage Type

      The valid values are Standard Cloud Storage, Performance Cloud Storage, Capacity Cloud Storage, Local SSD, and Local HDD. Select a storage class as needed. For more information, see Storage classes.

      • Standard: Suitable for scenarios that require real-time data access, such as feed streams, chats, real-time reports, and online computing.

      • Performance: Suitable for scenarios that require low-latency data access, such as ad bidding, user personas, audience segmentation, real-time search, and risk control.

      • Capacity Cloud Storage: Suitable for scenarios that require Infrequent Access to data, such as monitoring logs, historical orders, audio and video archiving, data lake storage, and offline computing.

      • Local SSD: Local disks are from a single physical server and provide low latency, high random IOPS, high throughput, and high cost-effectiveness. This storage class is suitable for online services such as online games, e-commerce, ApsaraVideo Live, and media. It meets the low latency and high I/O performance requirements of I/O-intensive applications for block storage.

      • Big Data: Local disks are from a single physical server and provide low latency, high random IOPS, high throughput, and high cost-effectiveness. This storage class is suitable for industries such as the internet and finance that have big data computing and storage analysis requirements. You can use this storage class for business scenarios that require mass data storage and offline computing.

      Storage Capacity

      Select the storage capacity for the instance.

      Instance Configurations

      Select the data engines. You can also click Edit in the upper-right corner of a card to modify the node type, node specifications, number of nodes, whether to mount a cloud disk, the cloud disk type, and the cloud disk capacity.

      Select the node specifications and number of nodes for the data engines as needed. For more information, see Select engine types and Select node specifications and the number of nodes.

      Whether to select capacity cloud storage

      Specifies whether to enable Capacity Cloud Storage for the instance. For more information, see Capacity Cloud Storage.

      Note

      The actual available storage capacity of cloud storage is the total capacity. Local disk clusters use a triplicate architecture. The actual available storage capacity is one-third of the total capacity.

      Capacity-based cloud storage capacity

      Select the capacity of the Capacity Cloud Storage for the instance.

      Note

      This parameter is required only if you set Whether to select capacity cloud storage to Yes.

      Whether to activate the computing engine

      Select whether to enable the compute engine.

      Duration

      If you create a subscription instance, select a subscription duration. You can select a duration of 1 to 9 months or 1 to 3 years.

      Note

      If you want to enable auto-renewal for the instance, select Auto-renewal. Make sure that your account has a sufficient balance before the instance expires.

      Resource Group

      Select a resource group to manage the instance. You can select an existing resource group or create a new one. For more information about how to create a resource group, see Create a resource group.

    Lindorm Tunnel Service

    1. In the Billing Method section, select Subscription or Pay-as-you-go.

      Note

      You can change the billing method in the console after the instance is created.

      • Subscription: A prepaid billing method where you pay for resources before you use them. This method is ideal for long-term use and is more cost-effective than the pay-as-you-go method. The longer the subscription duration, the greater the discount.

      • Pay-as-you-go: This billing method charges you hourly for the resources that you use. It is suitable for short-term use because you can release an instance at any time to save costs.

    2. Configure the instance parameters.

      Parameter

      Description

      Region and Zone

      Select the region where the instance resides.

      Note

      • You cannot change the region after the instance is created. Select the region with caution.

      • If your application is deployed on an ECS instance, select the same region as the ECS instance. Otherwise, the instances cannot communicate over the internal network.

      Zone

      Select the zone where the instance resides.

      Note

      If your application is deployed on an ECS instance, we recommend that you select the same zone as the ECS instance to reduce network latency.

      Network Type

      Fixed to VPC.

      VPC

      Select the VPC where the instance resides. If you do not have a VPC, you can create one in the VPC console. For more information, see Create and manage a VPC.

      vSwitch

      Select the vSwitch to which the instance is connected. If you do not have a vSwitch, you can create one in the VPC console. For more information, see Create a vSwitch.

      Cluster Name

      Set a name for the instance to identify it for your business.

      Node Specifications

      Select the node specifications as needed.

      Number Of Nodes

      Enter the number of nodes as needed.

      Duration

      If you create a subscription instance, select a subscription duration. You can select a duration of 1 to 9 months or 1 to 3 years.

      Note

      If you want to enable auto-renewal for the instance, select Auto-renewal. Make sure that your account has a sufficient balance before the instance expires.

      Resource Group

      Select a resource group to manage the instance. You can select an existing resource group or create a new one. For more information about how to create a resource group, see Create a resource group.

    1. After configuring the parameters, click Buy Now.

    2. On the Confirm Order page, review and accept the Terms of Service, and then click Activate Now.

    3. After the payment is complete, click Go To Console to open the Lindorm console.