Create an instance

Prerequisites

You must have an Alibaba Cloud account. For more information, see Sign up for an Alibaba Cloud account.

Free trial

Alibaba Cloud offers a free trial of Lindorm. You can visit Alibaba Cloud Free Trial to apply for the trial. For a tutorial on the free trial, see Lindorm free trial tutorial.

Usage notes

If your application runs on an ECS instance, ensure the Lindorm and ECS instances meet the following conditions for network connectivity. For information about how to view ECS instance details, see View instance information.

• The instances must be in the same region. We recommend deploying them in the same availability zone to reduce network latency.

• The instances use the same network type.

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

   For more information about the product types, see Product series.

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

   Note

   You can change the billing method in the console after creating the instance.

   • Subscription: A prepaid billing method where you are charged for resources before you use them. This billing method is suitable for long-term use. It is more cost-effective than the pay-as-you-go option and offers larger discounts for longer subscription periods.

   • Pay-as-you-go: A post-paid billing method where you are billed hourly based on your instance configuration. This method is suitable for short-term needs. You can release the instance at any time to save costs.

5. Configure the following parameters for the instance.

   Lindorm V1

   Parameter	Description
   Basic instance fee	Fixed to Lindorm Multi-modal Service.
   Deployment Method	Single-zone Deployment: The primary and secondary nodes are in the same availability zone. This mode is suitable for disaster recovery within a single data center. Multi-zone Deployment (HA): The primary and secondary nodes are in different availability zones. This mode provides cross-zone disaster recovery and supports only LindormTable. Multi-zone Deployment (Basic): The primary and secondary nodes are in different availability zones. This mode provides cross-zone disaster recovery and supports all engines.
   Region	Select the region where you want to deploy the instance. Note You cannot change the region after creating the instance. Choose the region carefully. If your application is deployed on an ECS instance, select the same region as the ECS instance to ensure direct communication over the internal network.
   Availability Zone	Select the availability zone for the instance. Note If your application is deployed on an ECS instance, we recommend that you select the same availability zone to reduce network 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 the VPC for the instance. If you do not have an available VPC, you can create one in the VPC console. For more information, see Create and manage a VPC.
   vSwitch	Select the vSwitch for the instance. If you do not have an available vSwitch, you can create one in the VPC console. For more information, see 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 the availability zones for the instance. The primary, secondary, and coordinator nodes must be in different availability 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 the vSwitch for the instance. 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 a name to identify the instance.
   Storage Type	The available storage types are Standard Cloud Storage, Performance Cloud Storage, Capacity Cloud Storage, local SSD, and Big Data. Select a storage type. For more information, see 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	The available data engines are LindormTable, LindormTSDB, Lindorm Search, and Lindorm Stream. You can select the node specifications and the number of nodes for each engine based on your business requirements. For more information, see Select engine types and 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	Specifies whether to enable capacity-optimized cloud storage for the instance. For more information, see Capacity-optimized cloud storage. Note Instances that use local disks have a three-replica architecture, so the available storage capacity is one-third of the total purchased capacity. For instances that use cloud storage, the available storage capacity is the total 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	Select whether to enable the compute engine.
   Subscription Length	If you create a subscription instance, select a subscription duration. You can select a duration from 1 to 9 months, or from 1 to 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 to manage the instance. You can select an existing resource group or create a new one. For more information, see Create a resource group.

   Lindorm

   Parameter	Description
   Deployment Scenario	Single Zone: The primary and secondary nodes are in the same availability zone. This mode is suitable for disaster recovery within a single data center. Multi-zone Deployment (HA): The primary and secondary nodes are in different availability zones. This mode provides cross-zone disaster recovery and supports only LindormTable. Multi-zone Deployment (Basic): The primary and secondary nodes are in different availability zones. This mode provides cross-zone disaster recovery and supports all engines.
   Instance name	Enter a name to identify the instance.
   Region Type	Select the region where you want to deploy the instance. Note You cannot change the region after creating the instance. Choose the region carefully. If your application is deployed on an ECS instance, select the same region as the ECS instance to ensure direct communication over the internal network.
   Availability Zone	Select the availability zone for the instance. Note If your application is deployed on an ECS instance, we recommend that you select the same availability zone to reduce network latency.
   VPC	Select the VPC for the instance. If you do not have an available VPC, you can create one in the VPC console. For more information, see Create and manage a VPC.
   Create a VPC.	Select the vSwitch for the instance. If you do not have an available vSwitch, you can create one in the VPC console. For more information, see 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 the availability zones for the instance. The primary, secondary, and coordinator nodes must be in different availability 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 the vSwitch for the instance. 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	The available storage types are Performance Cloud Storage, Standard Cloud Storage, Big Data, and local SSD. Select a storage type. For more information, see 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 the data engines. You can also click the icon in the upper-right corner of a card to modify settings such as its node type, specifications, number of nodes, and attached cloud disk configurations. You can select the node specifications and the number of nodes for each engine based on your business requirements. For more information, see Select engine types and 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. Specifies whether to enable capacity-optimized cloud storage for the instance. For more information, see Capacity-optimized cloud storage. Note Instances that use local disks have a three-replica architecture, so the available storage capacity is one-third of the total purchased capacity. For instances that use cloud storage, the available storage capacity is the total 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	Select whether to enable the compute engine.
   Duration	If you create a subscription instance, select a subscription duration. You can select a duration from 1 to 9 months, or from 1 to 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 to manage the instance. You can select an existing resource group or create a new one. For more information, see Create a resource group.

   LindormTunnel channel service

   Parameter	Description
   Region and Zone	Select the region where you want to deploy the instance. Note You cannot change the region after creating the instance. Choose the region carefully. If your application is deployed on an ECS instance, select the same region as the ECS instance to ensure direct communication over the internal network.
   Zone	Select the availability zone for the instance. Note If your application is deployed on an ECS instance, we recommend that you select the same availability zone to reduce network latency.
   Network Type	Fixed to VPC.
   Virtual Private Cloud (VPC)	Select the VPC for the instance. If you do not have an available VPC, you can create one in the VPC console. For more information, see Create and manage a VPC.
   vSwitch	Select the vSwitch for the instance. If you do not have an available vSwitch, you can create one in the VPC console. For more information, see Create a vSwitch.
   Cluster Name	Enter a name to identify the instance.
   Node Specifications	Select the required node specifications.
   Nodes	Enter the required number of nodes.
   Duration	If you create a subscription instance, select a subscription duration. You can select a duration from 1 to 9 months, or from 1 to 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 to manage the instance. You can select an existing resource group or create a new one. For more information, see 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.