Parameter | Description |
Product Type | Subscription: Recommended for long-term use of ES clusters. You make a one-time payment, and the price is lower than that of Pay-as-you-go. Pay-as-you-go: Suitable for short-term scenarios such as application development or feature testing. You are billed by the hour and can release the cluster at any time to stop billing. You can create a pay-as-you-go cluster first and switch it to Subscription after you confirm that the cluster meets your requirements.
|
Regions and Zones | Select a region based on your business requirements. The region cannot be changed after the cluster is created: The closer the region is to your users, the lower the network latency and the faster the access speed. If the ES cluster must communicate with other Alibaba Cloud services over an internal network, deploy the cluster and those services in the same region.
|
Number of Zones | 1-AZ: A standard deployment mode suitable for non-critical workloads. 2-AZ: A cross-zone disaster recovery deployment mode suitable for production workloads. 3-AZ (default): A high availability (HA) deployment mode suitable for production workloads with higher availability requirements. After you select two or three zones, the page displays the Zone 2 and Zone 3 configuration items. The default value is Random. Keep the default value to let the system assign zones automatically, or specify them manually. For more information, see Deploy and manage a multi-zone cluster.
|
Network Type | Only Virtual Private Cloud (VPC) is supported. |
VPC | Select a VPC in the selected region: (Recommended) If the ES cluster must communicate with other Alibaba Cloud services over an internal network, deploy the cluster and those services in the same VPC. If no VPC meets your business requirements, create one first. For more information, see Create a VPC and a vSwitch.
|
Virtual Switch | Only vSwitches in the specified VPC and the same zone as the ES cluster are displayed. If no vSwitch meets your business requirements, create one first. For more information, see Create a VPC and a vSwitch. |
Cluster Type | Engine-enhanced edition: 100% compatible with open-source Elasticsearch and provides enterprise features such as X-Pack free of charge. It is optimized for search, logging, and AI scenarios, and you can enable its enhanced capabilities as needed. Cloud-native management improves change efficiency, and the intelligent O&M ES Agent is ready to use. Standard Edition: 100% compatible with open-source Elasticsearch and provides enterprise features such as X-Pack free of charge. It covers multiple ES versions from 5.x to 9.x. Cloud-native management improves change efficiency, and the intelligent O&M ES Agent is ready to use. For more information, see Features by version and Feature overview.
|
Elasticsearch Version | Engine-enhanced edition: Supports versions 9.4.0, 8.17.0, and 7.10.0, as well as the 9.x (Agent Engine Edition) version. Click Other to select versions 8.15.1, 7.16.2, or 6.7.0. Standard Edition: Supports versions 9.3.2, 8.13.4, 8.9.1, 8.5.1, 7.7.1, 6.8.23, and 5.6.16. For more information, see Version features comparison and Release Note. The regions and zones that each version supports may vary. The options displayed on the purchase page prevail.
|
Scenario selection and advanced features | Select a scenario based on your business type. The available scenarios depend on the Elasticsearch Version that you select. After you select a scenario, the page displays the advanced features that apply to that scenario and their billing methods. You can enable these features as needed: Search scenario: Suitable for common workloads that require high query performance. Advanced features for this scenario: FalconSeek high-performance search engine: Built on the Havenask search engine technology developed by Alibaba Group, it enhances the Elasticsearch kernel. It remains fully compatible with Elasticsearch syntax and ecosystem while providing higher search performance. It is free to enable and has no additional billable items. OpenStore storage engine (high-performance search): Uses high-performance shared storage and intelligent caching to ensure low-latency retrieval. Scaling does not require a complete migration of underlying data, which reduces the duration of cluster changes. Scheduled and on-demand elasticity allow compute resources to scale with business peaks and troughs. Billing is based on OpenStore storage space (DFS) and cache disk space. Logging scenario: Suitable for workloads with more writes than reads, time-series data, and long-term data storage and analysis requirements but low real-time requirements. Advanced features for this scenario: Indexing Service managed write service: Cloud-managed services increase elastic write throughput by more than 10 times. You do not need to reserve resources for peak write traffic, and you are billed based on actual write traffic, which reduces the cost of analyzing large volumes of logs. Billing is based on write traffic and managed storage space. OpenStore storage engine (log analytics): Uses object storage and intelligent caching to reduce the cost of retaining large volumes of logs over the long term. You do not need to reserve capacity in advance, and you can query historical data without restoring it. Billing is based on OpenStore storage space (OSS), with storage as low as CNY 0.15 per GB per month. AI scenario: This is the only scenario that the 9.x (Agent Engine Edition) version supports. In this case, you cannot select the search scenario or the logging scenario. Advanced features for this scenario: SliceCollection massive-scale multi-tenant search: Designed for agent retrieval and retrieval-augmented generation (RAG) workloads. A single cluster can hold tenant data at a scale of hundreds of millions, which makes it suitable for scenarios such as knowledge bases and code retrieval. It uses shared storage to implement storage-compute disaggregation and read/write splitting. You can scale write and query resources independently, and dormant data incurs only storage fees. Engine-enhanced edition and Standard Edition both require a scenario. Engine-enhanced edition provides the preceding advanced features, whereas Standard Edition does not provide advanced features. After the cluster is created, you can modify the scenario configuration as needed to optimize cluster and index configurations and reduce cluster exceptions and performance issues caused by improper configurations. For more information, see Modify a scenario-base configuration template. Functions and features vary by version. For more information, see Feature overview.
|
Deployment Mode | New cloud-native management mode: The deployment mode currently provided on the purchase page. It supports a broad range of cluster types and versions, provides out-of-the-box AI capabilities, and improves cluster O&M efficiency in areas such as scaling, monitoring, and alerting.
|
Specifications | Click each node section to configure nodes based on your business requirements. Configurable nodes include data nodes, Kibana nodes, dedicated master nodes, cold data nodes, client nodes, and frozen data nodes. The node specification family for data nodes depends on the scenario that you select: the search scenario uses the next-generation cloud disk type and the logging scenario uses the storage-compute disaggregated type. After the cluster is created, you cannot change the node specification family or scale node specifications across specification families. For guidance on selecting node specifications, see Evaluate specifications and storage capacity. For detailed descriptions of node configurations, see Configure nodes for an Alibaba Cloud Elasticsearch cluster. Click Reset to Default in the lower-right corner of the section to restore modified node configurations to the default configurations.
|
Resource Group | Resource groups allow you to manage ES clusters as groups. For more information, see Manage permissions with resource groups. |
Cluster Name | If you leave this field blank, the system automatically generates a name. You can change the cluster name on the Basic Information page after the cluster is created. |
Username | The default account is elastic and cannot be changed. This account has the super administrator (Superuser) role of the cluster. You can use it to access the ES cluster and log on to the Kibana console. If you change the password of the elastic account, the change takes effect immediately and interrupts all existing connections that use the account because authentication fails. If this password is hard-coded in a business application, services may become unavailable. For security and to follow the principle of least privilege, do not use the elastic account directly in production code or applications. Create roles and standard users with specific permission scopes in the Kibana console for business use. For more information, see Manage user permissions with X-Pack roles. |
Password | The password for the elastic account. This field cannot be empty. |
Subscription Duration | If the product type is Subscription, select a subscription duration. (Recommended) Enable Auto-renewal to prevent the cluster from stopping or being released when the resources expire. For monthly subscriptions, the Unified Auto Renewal Cycle is one month. For yearly subscriptions, the Unified Auto Renewal Cycle is one year. Available durations are one month, one year, two years, three years, and five years.
|