All Products
Search

This Product

    Lindorm:Create an instance

    Document Center

    Lindorm:Create an instance

    Last Updated:Jun 03, 2026

    You can create a Lindorm instance in the Lindorm console and configure parameters such as billing method, region, storage type, and data engines.

    Prerequisites

    You must have an Alibaba Cloud account.

    Network requirements

    If your application runs on an ECS instance, ensure the Lindorm and ECS instances meet these network requirements. View instance information.

    • Deploy in the same region. We recommend using the same availability zone to reduce latency.

    • The instances use the same network type.

    Note

    VPCs are recommended for enhanced security. Place the Lindorm and ECS instances in the same VPC.

    Procedure

    1. Log on to the Lindorm console.

    2. On the Instances page, click Create.

      Note

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

    3. In the Commodity Type section, select Lindorm V1, Lindorm, or LindormTunnel channel service.

      Note

      Learn about product types in Product series.

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

      Note

      You can change the billing method after instance creation.

      • Subscription: Pay upfront for long-term use. More cost-effective than pay-as-you-go, with larger discounts for longer periods.

      • Pay-as-you-go: Billed hourly based on instance configuration. Suitable for short-term use. Release the instance anytime to stop charges.

    5. Configure the instance parameters.

      Lindorm V1

      Parameter

      Description

      Basic instance fee

      Fixed to Lindorm Multi-modal Service.

      Deployment Method

      • Single-zone Deployment: Primary and secondary nodes in the same zone. Supports single-zone disaster recovery.

      • Multi-zone Deployment (HA): Primary and secondary nodes in different zones. Cross-zone disaster recovery. Supports LindormTable only.

      • Multi-zone Deployment (Basic): Primary and secondary nodes in different zones. Cross-zone disaster recovery. Supports all engines.

      Region

      Select the deployment region.

      Note

      • The region cannot be changed after creation. Choose carefully.

      • If your application runs on ECS, select the same region for internal network connectivity.

      Availability Zone

      Select an availability zone.

      Note

      If your application runs on ECS, we recommend selecting the same zone to minimize latency.

      Multi-zone

      This parameter is displayed only when Deployment Method is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

      Network Type

      Fixed to VPC.

      VPC

      Select a VPC. If needed,Create and manage a VPC.

      vSwitch

      Select a vSwitch. If needed,Create a vSwitch.

      Note

      This parameter is not available if Deployment Method is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

      Primary Zone

      Select availability zones. Primary, secondary, and coordinator nodes must be in different zones.

      Note

      This parameter is displayed only when Deployment Method is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

      Secondary Zone

      Client Node Zone

      vSwitch for Primary Zone

      Select a vSwitch.

      Note

      This parameter is displayed only when Deployment Method is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

      vSwitch for Secondary Zone

      vSwitch for Client Node Zone

      Cluster Name

      Enter an instance name.

      Storage Type

      Available types: Standard Cloud Storage, Performance Cloud Storage, Capacity Cloud Storage, local SSD, and Big Data. Storage types.

      • 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 profiles, audience segmentation, real-time search, and risk control systems.

      • Capacity: 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: This type uses local disks on a single physical server and provides low latency, high random IOPS, high throughput, and high cost-effectiveness. It is suitable for I/O-intensive online services like online games, e-commerce, live video streaming, and media.

      • Big Data: This type uses local disks on a single physical server and provides low latency, high random IOPS, high throughput, and high cost-effectiveness. It is suitable for industries such as internet and finance that require large-scale data storage and offline computation for massive datasets.

      Select Engine Type

      Available engines: LindormTable, LindormTSDB, Lindorm Search, and Lindorm Stream. Select node specifications and count per engine. Select engine types. Select node specifications and number of nodes.

      • LindormTable: Select the Node Spec of Wide Table Engine (HBase/Cassandra APIs) and Wide Table Nodes as needed.

      • LindormTSDB: Select the Node Spec of Time Series Engine (TSDB API) and Time Series Engine Nodes as needed.

      • Lindorm Search: Select the Node Spec of Search Engine (Solr API) and Search Engine Nodes as needed.

      • Lindorm Stream: Select the Node Specifications of Streaming Engine Nodes and Number of Streaming Engine Nodes as needed.

      Note

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

      • If Storage Type is set to Big Data, you cannot select Lindorm Stream.

      Storage Space

      Select the storage capacity for the instance.

      Purchase Capacity Storage

      Enable or disableCapacity-optimized cloud storage.

      Note

      Local-disk instances use three replicas, so usable capacity is one-third of the total. Cloud storage instances use the full purchased capacity.

      Capacity Storage

      Select the capacity for the capacity-optimized cloud storage.

      Note

      This parameter is required only if you select Purchase Capacity Storage for the Yes parameter.

      Whether to activate the computing engine

      Enable or disable the compute engine.

      Subscription Length

      For subscription instances, select a duration: 1-9 months or 1-3 years.

      Note

      If you want the instance to be automatically renewed upon expiration, select Auto-renewal Recommended and ensure that your account has a sufficient balance before the instance expires.

      Resource Group

      Select a resource group.Create a resource group.

      Lindorm

      Parameter

      Description

      Deployment Scenario

      • Single Zone: Primary and secondary nodes in the same zone. Supports single-zone disaster recovery.

      • Multi-zone Deployment (HA): Primary and secondary nodes in different zones. Cross-zone disaster recovery. Supports LindormTable only.

      • Multi-zone Deployment (Basic): Primary and secondary nodes in different zones. Cross-zone disaster recovery. Supports all engines.

      Instance name

      Enter an instance name.

      Region Type

      Select the deployment region.

      Note

      • The region cannot be changed after creation. Choose carefully.

      • If your application runs on ECS, select the same region for internal network connectivity.

      Availability Zone

      Select an availability zone.

      Note

      If your application runs on ECS, we recommend selecting the same zone to minimize latency.

      VPC

      Select a VPC. If needed,Create and manage a VPC.

      Create a VPC.

      Select a vSwitch. If needed,Create a vSwitch.

      Note

      This parameter is not available if Deployment Scenario is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

      Primary Zone

      Select availability zones. Primary, secondary, and coordinator nodes must be in different zones.

      Note

      This parameter is displayed only when Deployment Scenario is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

      Secondary Zone

      Coordinator Node Zone

      Primary AZ Switch

      Select a vSwitch.

      Note

      This parameter is displayed only when Deployment Scenario is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

      Standby zone switch

      Coordination Node Availability Zone Switch

      Storage Type

      Available types: Performance Cloud Storage, Standard Cloud Storage, Big Data, and local SSD. Storage types.

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

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

      • Big Data: This type uses local disks on a single physical server and provides low latency, high random IOPS, high throughput, and high cost-effectiveness. It is suitable for industries such as internet and finance that require large-scale data storage and offline computation for massive datasets.

      • Local SSD: This type uses local disks on a single physical server and provides low latency, high random IOPS, high throughput, and high cost-effectiveness. It is suitable for I/O-intensive online services like online games, e-commerce, live video streaming, and media.

      Note

      This parameter is displayed only when Deployment Scenario is set to Single Zone.

      Instance Configuration

      Select data engines. Click the image.png icon in the upper-right corner of a card to modify node type, specifications, count, and cloud disk settings.

      Select node specifications and count per engine. Select engine types. Select node specifications and number of nodes.

      Whether to select 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.

      Enable or disableCapacity-optimized cloud storage.

      Note

      Local-disk instances use three replicas, so usable capacity is one-third of the total. Cloud storage instances use the full purchased capacity.

      Capacity-based cloud storage capacity

      Select the capacity for the capacity-optimized cloud storage.

      Note

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

      Whether to activate the computing engine

      Enable or disable the compute engine.

      Duration

      For subscription instances, select a duration: 1-9 months or 1-3 years.

      Note

      If you want the instance to be automatically renewed upon expiration, select Auto-renewal Recommended and ensure that your account has a sufficient balance before the instance expires.

      Resource Group

      Select a resource group.Create a resource group.

      LindormTunnel channel service

      Parameter

      Description

      Region and Zone

      Select the deployment region.

      Note

      • The region cannot be changed after creation. Choose carefully.

      • If your application runs on ECS, select the same region for internal network connectivity.

      Zone

      Select an availability zone.

      Note

      If your application runs on ECS, we recommend selecting the same zone to minimize latency.

      Network Type

      Fixed to VPC.

      Virtual Private Cloud (VPC)

      Select a VPC. If needed,Create and manage a VPC.

      vSwitch

      Select a vSwitch. If needed,Create a vSwitch.

      Cluster Name

      Enter an instance name.

      Node Specifications

      Select the required node specifications.

      Nodes

      Enter the required number of nodes.

      Duration

      For subscription instances, select a duration: 1-9 months or 1-3 years.

      Note

      If you want the instance to be automatically renewed upon expiration, select Auto-renewal Recommended and ensure that your account has a sufficient balance before the instance expires.

      Resource Group

      Select a resource group.Create a resource group.

    6. After you configure the parameters, click Buy Now.

    7. On the Confirm Order page, review and accept the terms of service, then click Pay.

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