Instance Specifications

2 vCPUs | 1 GiB

40 GiB | General Purpose SSD

30 Mbit/s | 2084 GB

The following service resources can be purchased together with FlexusL instances:

• Data disk: General Purpose SSD V2 | Custom capacity
• HSS: Basic edition
• CBR: Server backup | Custom vault capacity

2 vCPUs | 2 GiB

60 GiB | General Purpose SSD

30 Mbit/s | 3072 GB

2 vCPUs | 4 GiB

80 GiB | General Purpose SSD

30 Mbit/s | 4096 GB

2 vCPUs | 8 GiB

160 GiB | General Purpose SSD

30 Mbit/s | 5120 GB

4 vCPUs | 8 GiB

240 GiB | General Purpose SSD

30 Mbit/s | 6144 GB

4 vCPUs | 16 GiB

320 GiB | General Purpose SSD

30 Mbit/s | 7168 GB

System disk

General Purpose SSD

• Each FlexusL instance can only have one system disk attached.
• The system disk cannot be expanded or detached, and no more system disks can be attached.

Data disk

General Purpose SSD V2

• Each FlexusL instance can only have one data disk attached.
• Data disks can only be attached or expanded on the FlexusL console. Existing data disks cannot be attached to FlexusL instances.
• Data disks cannot be detached.

Private network

• After a FlexusL instance is created, a fixed VPC is configured for it by default. You cannot customize the VPC.
• By default, FlexusL instances created by the same account in the same region are located in the same VPC. They can communicate with each other over a private network.

  When cloud resources (such as ECSs and cloud databases) created by the same account in the same region are located in the same VPC (vpc-default-smb) as FlexusL instances, they can communicate with each other over a private network. If they are not in the same VPC, they can communicate with each other through peering connection. For details, see VPC Peering Connection Usage Examples.

• FlexusL instances that are created by different accounts or located in different regions are located in different VPCs and they cannot communicate with each other over a private network. To access FlexusL instances and cloud resources in other VPCs, you can use the following methods:
  • Cloud Connect: enables cross-account or cross-region access with other FlexusL instances or cloud resources (such as ECSs and cloud databases). For details, see Cloud Connect.
  • Peering connection: enables intra-account or cross-account access with other FlexusL instances or cloud resources in the same region. For details, see VPC Peering Connection Usage Examples.
• The private IP address of a FlexusL instance cannot be changed.

EIP

After a FlexusL instance is created, a fixed elastic IP address (EIP) is assigned by default. The EIP has the following constraints:

• The EIP of the FlexusL instance cannot be unbound or changed.
• The EIP will not be retained after the FlexusL instance is released.
• IPv6 addresses cannot be configured for FlexusL instances.

Data package

A monthly data package is included in the FlexusL instance. Any traffic usage in excess of the package is billed on a pay-per-use basis. Data packages cannot be purchased or upgraded separately.

• EIPs are billed by traffic. You cannot change the EIP billing mode.

• Only outbound traffic (originating from your server) will be billed.
• The data package included in the FlexusL service package 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.

• 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 based on a tiered pricing model, 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, the excess traffic will no longer generate costs.

Peak EIP bandwidth

• Outbound peak bandwidth
  • The peak bandwidth in the FlexusL service package refers to the outbound peak bandwidth, that is, the maximum bandwidth for the FlexusL instance to access the Internet.
  • The peak bandwidth cannot be changed separately.
  NOTE:

  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.