Instance Specifications
This section describes the resources contained in a FlexusL service package.
Instance Specifications
A cloud server packaged in a FlexusL instance uses the x86 architecture, KVM virtualization, and the same underlying hardware resources as an ECS. It delivers the same compute performance as an ECS with the same vCPUs and memory.
You can associate EVS disks, HSS, or CBR vaults with your FlexusL instance as needed. After a FlexusL instance is created, a fixed elastic IP address (EIP) is assigned by default. Multiple instance specifications are available. For details, see Table 1.
vCPUs | Memory |
System Disk Capacity | Type |
Peak Bandwidth | Data Package |
(Optional) Associated Service Resource |
---|---|---|---|
2 vCPUs | 0.5 GiB |
20 GiB | General Purpose SSD |
30 Mbit/s | 1,024 GB |
The following service resources can be purchased together with FlexusL instances:
|
2 vCPUs | 1 GiB |
40 GiB | General Purpose SSD |
30 Mbit/s | 2,084 GB |
|
2 vCPUs | 2 GiB |
60 GiB | General Purpose SSD |
30 Mbit/s | 3,072 GB |
|
2 vCPUs | 4 GiB |
80 GiB | General Purpose SSD |
30 Mbit/s | 4,096 GB |
|
2 vCPUs | 8 GiB |
160 GiB | General Purpose SSD |
30 Mbit/s | 5,120 GB |
|
4 vCPUs | 8 GiB |
240 GiB | General Purpose SSD |
30 Mbit/s | 6,144 GB |
|
4 vCPUs | 16 GiB |
320 GiB | General Purpose SSD |
30 Mbit/s | 7,168 GB |
Rules for using data packages provided by FlexusL are as follows:
- The data package provided by FlexusL is a monthly package. A monthly data package starts on the date of purchase and ends at 23:59:59 on the same day of the next month. For example, if you purchase a FlexusL instance at 10:00:00 on June 5, the expiration time of the package is at 23:59:59 (the last second of the day) on July 5. The package for the next month starts from 23:59:59 on July 5 to 23:59:59 on August 5.
- The data package provided by FlexusL covers the expenditures generated by outbound traffic.
Only outbound traffic (originating from your server) will be billed.
- Service traffic is preferentially deducted from the data package. Any traffic usage in excess of the package is billed by traffic. The excess traffic is billed in tiered pricing mode, and the unit price varies in different regions.
- The traffic quota is reset each month. Any unused portion of the data package cannot be rolled over to the next month.
- After you unsubscribe from or stop a FlexusL instance, no excess traffic will be generated.
- The peak bandwidth is not used as a service commitment and is only used as a reference for the bandwidth upper limit. If resource contention occurs, the peak bandwidth may be limited.
- Inbound peak bandwidth
- If the outbound peak bandwidth of a package is not greater than 10 Mbit/s, the inbound peak bandwidth is 10 Mbit/s.
- If the outbound peak bandwidth of a package is greater than 10 Mbit/s, the inbound peak bandwidth is the same as the outbound peak bandwidth.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot