Lindorm is available in the following series: Lindorm, Lindorm New Edition, and Lindorm Tunnel Service (LTS). This topic describes how to create an instance of each series in the Lindorm console.
To create an instance using the API or an SDK instead, see CreateLindormInstance and the SDK reference.
Prerequisites
Before you begin, ensure that you have:
An Alibaba Cloud account
(For RAM users) The required RAM permissions for the target series and billing method: To view or update a RAM user's permissions, see View the information about a RAM user and Grant permissions to a RAM user.
| Series | Billing method | Required permissions |
|---|
| Lindorm or Lindorm New Edition | Subscription | AliyunLindormFullAccess, AliyunHBaseReadOnlyAccess, AliyunBSSOrderAccess |
| Lindorm or Lindorm New Edition | Pay-as-you-go | AliyunLindormFullAccess, AliyunHBaseReadOnlyAccess |
A VPC and vSwitch in the target region and zone. If none exist, create them before purchasing an instance.
Choose an instance type
Select the series and deployment method that matches your workload, then follow the corresponding creation guide in the sections below.
| Series | Deployment method | Supported engines | Best for |
|---|
| Lindorm New Edition | Single-zone | Wide table, time series, LTS | Individual developers and small to medium enterprises for production, testing, or learning |
| Lindorm | Single-zone | Wide table, time series, search, file, compute, streaming | Large enterprise production workloads (IoV, IoT, IIoT, risk control, billing, advertising) |
| Lindorm or Lindorm New Edition | Multi-zone Basic Edition | All engines (Lindorm); wide table, time series, LTS (Lindorm New Edition) | Zone-level disaster recovery with support for multiple engines |
| Lindorm | Multi-zone Deployment (High-availability Edition) | Wide table only | Zone-level disaster recovery requiring the highest availability for the wide table engine |
| LTS | Single-zone | LTS tunnel | Data migration, change tracking, backup, and restoration |
For a detailed comparison of series and their use cases, see Series.
Create a Lindorm New Edition instance
Lindorm New Edition is suitable for large and medium enterprises running production workloads, individual developers learning Lindorm features, and small enterprises doing feature verification or testing.
Important You cannot downgrade specifications or reduce the number of nodes after creation. Size your instance based on your actual requirements.
Go to the Lindorm buy page and select Lindorm New Edition Available for Purchase under Product Type.
Set Billing Method to Subscription or Pay-as-you-go.
Subscription: Pay upfront for a fixed term. More cost-effective for long-term use, with larger discounts for longer periods.
Pay-as-you-go: Billed hourly by instance specification. Suitable for short-term use. Release the instance when no longer needed to stop charges.
You can change the billing method after the instance is created. See Billing methods.
Set Edition to Production or Test, and set Deployment Method to Single-zone Deployment.
Select an edition based on your business requirements. For the differences between production and test instances, see Series.
Configure the network settings.
| Parameter | Description |
|---|
| Region | The region where the instance is deployed. Select the region closest to your users to reduce latency. If you use multiple Alibaba Cloud services connected over VPCs, select the same region as those services. The region cannot be changed after creation. |
| Zone | The zone where the instance is deployed. Services in different zones within the same region can communicate over VPCs. |
| Network Type | Set to VPC (the only option). |
| VPC | The VPC to deploy the instance in. If you use other Alibaba Cloud services such as ECS, select the same VPC to enable communication. If no VPCs appear, verify that a VPC exists in the selected region and that your RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. |
| vSwitch | The vSwitch to connect to the instance. If no vSwitches appear, verify that a vSwitch exists in the selected zone and that your RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. |
| Instance Name | A name for identifying and managing the instance. |
Under Instance Configuration, select one or more engines based on your requirements. Click the icon in the upper-right corner of an engine card to configure the node specification, node count, disk attachment, disk type, and disk capacity. For engine descriptions and use cases, see Engines and Overview.
Important - The engines shown during purchase are required engines. You can activate additional engines after the instance is created. - Disks cannot be attached to LTS engine nodes.
(Subscription only) Set the subscription duration and enable auto-renewal if needed. Enable auto-renewal to prevent the instance from being released after it expires. For more information, see Expiration and overdue payments and Enable auto-renewal.
Important The RAM user must have the AliyunBSSOrderAccess permission to pay for a subscription order.
(Optional) Assign the instance to a resource group. Resource groups let you manage resources, control access permissions, and track costs. See What is Resource Group?
Complete the purchase on the buy page.
Create a single-zone Lindorm instance
Single-zone Lindorm instances are deployed as distributed clusters supporting all engines. Use this option for large enterprise production workloads, including Internet of Vehicles (IoV), Internet of Things (IoT), Industrial Internet of Things (IIoT), risk control, billing, advertising, feeds, and data dashboard scenarios.
Important The storage type cannot be changed after creation. Select the appropriate storage type before purchasing.
Go to the Lindorm buy page and select Lindorm under Product Type.
Set Billing Method to Subscription or Pay-as-you-go.
Subscription: Pay upfront for a fixed term. More cost-effective for long-term use, with larger discounts for longer periods.
Pay-as-you-go: Billed hourly by instance specification. Suitable for short-term use. Release the instance when no longer needed to stop charges.
You can change the billing method after the instance is created. See Billing methods.
Set Deployment Method to Single-zone Deployment, then configure the following parameters.
| Parameter | Description |
|---|
| Deployment Method | Select Single-zone Deployment. Primary and secondary nodes are deployed in the same zone, providing single-data center disaster recovery. |
| Region | The region where the instance is deployed. Select the region closest to your users to reduce latency. If you use multiple Alibaba Cloud services connected over VPCs, select the same region as those services. The region cannot be changed after creation. |
| Zone | The zone where the instance is deployed. Services in different zones within the same region can communicate over VPCs. |
| Network Type | Set to VPC (the only option). |
| VPC | The VPC to deploy the instance in. If you use other Alibaba Cloud services such as ECS, select the same VPC to enable communication. If no VPCs appear, verify that a VPC exists in the selected region and that your RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. |
| vSwitch | The vSwitch to connect to the instance. If no vSwitches appear, verify that a vSwitch exists in the selected zone and that your RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. |
| Cluster Name | A name for identifying and managing the instance. |
Set the Storage Type. The storage type determines access latency, supported engines, and pricing. For a comparison of storage types, see Storage types.
Select the engine specification and node count under Lindorm engines. Lindorm instances run as distributed clusters. Each engine requires at least two nodes. Set the node count to 0 for engines you do not need.
Important After the instance is created, you can add nodes, increase specifications, and activate additional engines. You cannot deactivate engines that have already been activated.
Configure the storage capacity. The configuration method depends on the storage type you selected. Standard, Performance, or Capacity storage Local SSD or local HDD storage
Storage Space: The actual usable data capacity. For example, if you purchase 200 GiB and compress 100 GiB of data to 50 GiB, only 50 GiB of storage is used and 150 GiB of free storage capacity is available.
Disk Capacity of Each Node: Read-only. This value is determined by the node specification and count. To supplement local disk capacity without adding nodes, attach cloud disks. Instances using local disks use a triple-replica architecture. The usable capacity is one-third of the total disk capacity shown in the console. For example, with 3 nodes at 894 GB each, the console shows 2,682 GiB total, but the usable capacity is 894 GB. To improve storage utilization, enable erasure coding. See Storage types.
Purchase Cold Storage (optional): Capacity storage for infrequently accessed historical data. You can add cold storage now or after the instance is created.
Attach Disk (optional): Attach cloud disks if local disk capacity is insufficient and you do not want to add nodes. Attached cloud disks also use triple-replica architecture, so the usable capacity is one-third of the attached disk capacity shown in the console.
Capacity storage and cloud disk attachment are not supported for instances using local HDD storage.
(Subscription only) Set the subscription duration and enable auto-renewal if needed. Enable auto-renewal to prevent the instance from being released after it expires. For more information, see Expiration and overdue payments and Enable auto-renewal.
Important The RAM user must have the AliyunBSSOrderAccess permission to pay for a subscription order.
(Optional) Assign the instance to a resource group.
Complete the purchase on the buy page.
Create a multi-zone Lindorm instance (Basic Edition)
Multi-zone Basic Edition instances deploy wide table replicas across multiple zones using a replica consensus protocol, providing zone-level disaster recovery. This option supports all engines and is available for both the Lindorm and Lindorm New Edition product types.
Important The storage type cannot be changed after creation. Select the appropriate storage type before purchasing.
Go to the Lindorm buy page and select Lindorm or Lindorm New Edition Available for Purchase under Product Type.
Set the Billing Method:
You can change the billing method after the instance is created. See Billing methods.
Set Deployment Method to Multi-zone Basic Edition, then configure the following parameters.
| Parameter | Description |
|---|
| Deployment Method | Select Multi-zone Basic Edition. Each wide table region has an individual replica in all zones. Replicas are synchronized using the replica consensus protocol. |
| Region | The region where the instance is deployed. Select the region closest to your users to reduce latency. If you use multiple Alibaba Cloud services connected over VPCs, select the same region as those services. |
| Multi-zone Deployment | The combination of zones to deploy the instance across. |
| Network Type | Set to VPC (the only option). |
| VPC | The VPC to deploy the instance in. If you use other Alibaba Cloud services such as ECS, select the same VPC to enable communication. If no VPCs appear, verify that a VPC exists in the selected region and that your RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. |
| Primary Zone | The primary zone for wide table region replicas. |
| vSwitch for Primary Zone | The vSwitch for the primary zone. |
| Secondary Zone | The secondary zone for wide table region replicas. Replicas in primary and secondary zones are synchronized using the replica consensus protocol. |
| vSwitch for Secondary Zone | The vSwitch for the secondary zone. |
| Coordinator Node Zone | The zone for the coordinator node. The log node is also deployed in this zone. |
| vSwitch | The vSwitch for the coordinator node zone. |
| Cluster Name | A name for identifying and managing the instance. |
Set the Storage Type. For a comparison of storage types, see Storage types.
Select the engine specification and node count. For Lindorm instances: Select one or more engines. Each engine requires at least two nodes. Set the node count to 0 for engines you do not need. Click the icon to configure the node specification, node count, cloud disk attachment, disk type, and disk capacity. For engine descriptions and use cases, see Engines. For Lindorm New Edition instances: Select one or more engines. All engines run on independent nodes in a distributed cluster. Each engine requires at least two nodes (or at least three when using local disks). For engine descriptions and use cases, see Engines.
The Storage Type selector is not shown when Product Type is set to Lindorm New Edition Available for Purchase.
Configure the storage capacity. Standard, Performance, or Capacity storage Local SSD or local HDD storage
Storage Space: The actual usable data capacity. You can scale storage up or down after creation without migrating data.
Disk Capacity of Each Node: Read-only. Determined by the node specification and count. To supplement local disk capacity without adding nodes, attach cloud disks. Instances using local disks use a triple-replica architecture. The usable capacity is one-third of the total disk capacity shown in the console.
Purchase Cold Storage (optional): Capacity storage for infrequently accessed historical data.
Attach Disk (optional): Attach cloud disks if local disk capacity is insufficient.
Capacity storage and cloud disk attachment are not supported for instances using local HDD storage.
(Subscription only) Set the subscription duration and enable auto-renewal if needed. Enable auto-renewal to prevent the instance from being released after it expires. For more information, see Expiration and overdue payments and Enable auto-renewal.
Important The RAM user must have the AliyunBSSOrderAccess permission to pay for a subscription order.
(Optional) Assign the instance to a resource group.
Complete the purchase on the buy page.
Create a multi-zone Lindorm instance (High-availability Edition)
Multi-zone High-availability Edition instances deploy wide table replicas across multiple zones using a replica consensus protocol, providing the highest zone-level availability.
Important This deployment method supports the wide table engine only. For other engines, create a single-zone instance. The storage type cannot be changed after creation.
Go to the Lindorm buy page and select Lindorm under Product Type.
Set Billing Method to Subscription or Pay-as-you-go.
You can change the billing method after the instance is created. See Billing methods.
Set Deployment Method to Multi-zone Deployment, then configure the following parameters.
| Parameter | Description |
|---|
| Deployment Method | Select Multi-zone Deployment. Each wide table region has an individual replica in all zones. Replicas are synchronized using the replica consensus protocol. |
| Region | The region where the instance is deployed. Select the region closest to your users to reduce latency. If you use multiple Alibaba Cloud services connected over VPCs, select the same region as those services. |
| Multi-zone Deployment | The combination of zones to deploy the instance across. |
| Network Type | Set to VPC (the only option). |
| VPC | The VPC to deploy the instance in. If you use other Alibaba Cloud services such as ECS, select the same VPC to enable communication. If no VPCs appear, verify that a VPC exists in the selected region and that your RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. |
| Primary Zone | The primary zone for wide table region replicas. |
| vSwitch for Primary Zone | The vSwitch for the primary zone. |
| Secondary Zone | The secondary zone for wide table region replicas. Replicas in primary and secondary zones are synchronized using the replica consensus protocol. |
| vSwitch for Secondary Zone | The vSwitch for the secondary zone. |
| Coordinator Node Zone | The zone for the coordinator node. The log node is also deployed in this zone. |
| vSwitch | The vSwitch for the coordinator node zone. |
| Cluster Name | A name for identifying and managing the instance. |
Set the Storage Type. For a comparison of storage types, see Storage types.
Select the engine specification and node count under Lindorm engines. Standard or Performance storage Local SSD or local HDD storage
Node Spec of Wide Table Engine and Wide Table Nodes: Wide table engine nodes are distributed across the primary and secondary zones. The node count must be a multiple of two, with at least two nodes per zone. For guidance on selecting specifications and node counts, see Select the number and specification of nodes.
Log Node Specifications and Log Nodes: Log nodes store WAL logs for tables with strong consistency. They cannot be directly accessed by users. Keep the default values unless you have large data volumes — in that case, contact technical support.
Node Spec of Local Disk and Wide Table Nodes: The wide table engine is deployed on local disk nodes.
Log Node Specifications and Log Nodes: Keep the default values unless you have large data volumes.
Configure the storage capacity. Standard or Performance storage Local SSD or local HDD storage
Storage per Core Node: The available storage capacity is half of this value multiplied by the node count. For example, if the Storage per Core Node parameter is set to 1,000 GiB and the number of nodes is 3, the available storage capacity is 1,500 GiB (1,000 × 3 ÷ 2).
Log Node Disk Type and Storage per Log Node: Select a disk type for log nodes — ESSD (Enhanced SSD) for high-frequency access or high I/O workloads, or Ultra Disk for I/O-intensive scenarios.
Disk Capacity of Each Node: Read-only. Determined by the node specification and count. Instances using local disks use a triple-replica architecture, so the usable capacity is one-third of the disk capacity shown in the console. For example, with 3 nodes at 894 GB each, the console shows 2,682 GiB total, but the usable capacity is 894 GB. To improve storage utilization, enable erasure coding. See Storage types.
Capacity storage is not supported for multi-zone Lindorm instances.
(Subscription only) Set the subscription duration and enable auto-renewal if needed. Enable auto-renewal to prevent the instance from being released after it expires. For more information, see Expiration and overdue payments and Enable auto-renewal.
Important The RAM user must have the AliyunBSSOrderAccess permission to pay for a subscription order.
(Optional) Assign the instance to a resource group.
Complete the purchase on the buy page.
Create an LTS instance
Lindorm Tunnel Service (LTS) instances provide data migration, change tracking, and data backup and restoration.
Go to the Lindorm buy page and select Lindorm Tunnel Service under Product Type.
Set Billing Method to Subscription or Pay-as-you-go.
Subscription: Pay upfront for a fixed term. More cost-effective for long-term use, with larger discounts for longer periods.
Pay-as-you-go: Billed hourly by instance specification. Suitable for short-term use. Release the instance when no longer needed to stop charges.
You can change the billing method after the instance is created. See Billing methods.
Configure the network settings.
| Parameter | Description |
|---|
| Region | The region where the instance is deployed. Select the region closest to your users to reduce latency. If you use multiple Alibaba Cloud services connected over VPCs, select the same region as those services. The region cannot be changed after creation. |
| Zone | The zone where the instance is deployed. ECS instances and Lindorm instances in different zones can still communicate. To minimize latency for applications running on ECS, deploy the LTS instance in the same zone. |
| Network Type | Set to VPC (the only option). |
| VPC | The VPC to deploy the instance in. If you use other Alibaba Cloud services such as ECS, select the same VPC to enable communication. If no VPCs appear, verify that a VPC exists in the selected region and that your RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. |
| vSwitch | The vSwitch to connect to the instance. If no vSwitches appear, verify that a vSwitch exists in the selected zone and that your RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. |
| Cluster Name | A name for identifying and managing the instance. |
Select the node specification and count.
(Subscription only) Set the subscription duration and enable auto-renewal if needed. Enable auto-renewal to prevent the instance from being released after it expires. For more information, see Expiration and overdue payments and Enable auto-renewal.
Important The RAM user must have the AliyunBSSOrderAccess permission to pay for a subscription order.
(Optional) Assign the instance to a resource group.
Complete the purchase on the buy page.
FAQ
The buy page shows "inventory resources are insufficient." What should I do?
Resources in the selected zone are temporarily unavailable. Create the instance in a different zone.
The buy page shows an authentication failure. What should I do?
Your RAM user is missing required permissions. The permissions depend on the series and billing method:
Lindorm or Lindorm New Edition (subscription): AliyunLindormFullAccess, AliyunHBaseReadOnlyAccess, AliyunBSSOrderAccess
Lindorm or Lindorm New Edition (pay-as-you-go): AliyunLindormFullAccess, AliyunHBaseReadOnlyAccess
Contact your Alibaba Cloud account owner to grant the missing permissions. See Grant permissions to a RAM user.
Why can't I select VPCs or vSwitches?
Either no VPC or vSwitch exists in the selected region and zone, or your RAM user lacks the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. Create the missing VPC or vSwitch, or have the account owner grant your RAM user these permissions.
The instance isn't showing up in the console after purchase. What should I do?
Instances typically become available about 20 minutes after purchase. If the instance is still missing after 20 minutes, check the Order Management page. If you received a refund, the instance creation failed — try purchasing again. If the issue persists, submit a ticket.
Am I charged for features I haven't explicitly enabled?
You are only charged when you enable billed features or perform configuration changes:
Billed features: Enabling the wide table engine's backup feature or activating the compute engine incurs additional fees. The console prompts you before enabling any billed feature. See Overview for the full list of billable items.
Configuration changes: Adding nodes, upgrading node specifications, or scaling up storage incurs additional fees. The console prompts you before applying changes. See Billing of configuration changes.
Can I stop an instance temporarily?
Lindorm instances cannot be stopped. If you no longer need an instance, release it to stop all charges.
Can I release an instance?
Yes. You can release Lindorm, Lindorm New Edition, and LTS instances at any time. You are no longer charged fees for the instance after it is released. See Release an instance.
What's next
To manage your instance after it is created, see the Lindorm user guide.
To create an instance using the API, see CreateLindormInstance.
To select the right engines for your workload, see Engines.
To choose a storage type, see Storage types.