This topic describes the i2, i2g, and i1 instance families with local SSDs. It also includes information about the instance types that belong to these instance families.

Description

Instances with local SSDs provide high I/O performance. They are suitable for scenarios that impose high demands on storage I/O performance and high availability architecture at the application level. For example, they are suitable for NoSQL databases, massively parallel processing (MPP) databases, and distributed file systems.

For enterprises that provide online services like online gaming, e-commerce, live video streaming, and media, instances with local SSDs can satisfy the high requirements of I/O-intensive applications over low latency and high I/O performance of block storage.

Features:
  • Provides tens of thousands or hundreds of thousands of low latency random read/write IOPS for large databases.
  • Offers a throughput of up to several gibibytes per second for sequential read/write operations in big data, concurrent computing, and other large dataset scenarios.
  • Local NVMe SSDs guarantee hundreds of thousands of random read/write IOPS with only several microseconds of latency.
When using instances with local SDDs, note the following:
  • The configurations of instances with local SSDs are fixed. Automatic switchover upon dedicated host failures is not supported for instances with local SSDs.
  • The number and capacity of local disks of an instance vary depending on the instance type. You cannot attach additional local disks to instances with local SSDs because instances with local SSDs can only use default local SSDs. You cannot detach a local disk from an instance with local SSDs and then attach it to another instance.
  • You cannot create a snapshot for local disks. If you need to create an image for the system disk and data disks of an instance with local SSDs, we recommend that you create an image through the snapshots of both the system disk and data disks (data disks must be non-local disks).
  • You cannot create an image for the system disk and data disks of an instance with local SSDs based on the instance ID. Therefore, you cannot use a custom image to create an instance with local SSDs.
  • You can attach an SSD disk to an instance with local SSDs. The capacity of the SSD disk is scalable.
  • A single point of failure (SPOF) may be evident at the application layer due to each local disk being attached to a single host machine, meaning data reliability is dependent on the reliability of the host machine. We recommend that you implement data redundancy at the application layer to guarantee data availability.
    Warning When you use a local disk to store data, there is a risk of data loss (for example, if a hardware fault occurs to the host machine). Therefore, we recommend you do not use a local disk to store any data that you need to keep for a long term. If your applications have no data reliability architecture, we recommend that you use cloud disks or Shared Block Storage in your instances to increase data reliability.
  • Operations made on an instance with local SSDs may affect the data stored on the local disk. For more information, see Local disks.

Instance family with local SSDs, i2

Features:
  • Optimized I/O performance
  • Supports SSDs and ultra disks
  • High-performance local NVMe SSDs with high IOPS, high I/O throughput, and low latency
  • 1:8 CPU-to-memory ratio, designed for high-performance databases
  • 2.5 GHz Intel ® Xeon ® Platinum 8163 (Skylake) processors
  • Higher network performance along with more computing capacity
  • Scenarios:
    • Online transaction processing (OLTP) and high-performance relational databases
    • NoSQL databases such as Cassandra and MongoDB
    • Search scenarios such as Elasticsearch
The following table describes the instance types that belong to the i2 instance family and specifications of these instance types.
Instance type vCPUs Memory (GiB) Local storage (GiB) Bandwidth (Gbit/s, inbound or outbound) Packet forwarding rate (Kpps, inbound or outbound) Supports IPv6 NIC queues ENIs (including one primary ENI) Private IP addresses for a single ENI
ecs.i2.xlarge 4 32.0 1 × 894 1.0 500 Yes 2 3 10
ecs.i2.2xlarge 8 64.0 1 × 1,788 2.0 1,000 Yes 2 4 10
ecs.i2.4xlarge 16 128.0 2 × 1,788 3.0 1,500 Yes 4 8 20
ecs.i2.8xlarge 32 256.0 4 × 1,788 6.0 2,000 Yes 8 8 20
ecs.i2.16xlarge 64 512.0 8 × 1,788 10.0 4,000 Yes 16 8 20
Note

Instance family with local SSDs, i2g

Features:
  • Optimized I/O performance
  • Supports SSDs and ultra disks
  • High-performance local NVMe SSDs with high IOPS, high I/O throughput, and low latency
  • 1:4 CPU-to-memory ratio, designed for high-performance databases
  • 2.5 GHz Intel ® Xeon ® Platinum 8163 (Skylake) processors
  • Higher network performance along with more computing capacity
  • Scenarios:
    • OLTP and high-performance relational databases
    • NoSQL databases such as Cassandra and MongoDB
    • Search scenarios such as Elasticsearch
The following table describes the instance types that belong to the i2g instance family and specifications of these instance types.
Instance type vCPUs Memory (GiB) Local storage (GiB) Bandwidth (Gbit/s, inbound or outbound) Packet forwarding rate (Kpps, inbound or outbound) Supports IPv6 NIC queues ENIs (including one primary ENI) Private IP addresses for a single ENI
ecs.i2g.2xlarge 8 32.0 1 × 894 2.0 1,000 No 2 4 10
ecs.i2g.4xlarge 16 64.0 1 × 1,788 3.0 1,500 No 4 8 20
ecs.i2g.8xlarge 32 128.0 2 × 1,788 6.0 2,000 No 8 8 20
ecs.i2g.16xlarge 64 256.0 4 × 1,788 10.0 4,000 No 16 8 20
Note

Instance family with local SSDs, i1

Features:
  • Optimized I/O performance
  • Supports SSDs and ultra disks
  • High-performance local NVMe SSDs with high IOPS, high I/O throughput, and low latency
  • 1:4 CPU-to-memory ratio, designed for high-performance databases
  • 2.5 GHz Intel ® Xeon ® E5-2682 v4 (Broadwell) processors
  • Higher network performance along with more computing capacity
  • Scenarios:
    • Online transaction processing (OLTP) and high-performance relational databases
    • NoSQL databases such as Cassandra and MongoDB
    • Search scenarios such as Elasticsearch
The following table describes the instance types that belong to the i1 instance family and specifications of these instance types.
Instance type vCPUs Memory (GiB) Local storage (GiB) Bandwidth (Gbit/s, inbound or outbound) Packet forwarding rate (Kpps, inbound or outbound) Supports IPv6 NIC queues ENIs (including one primary ENI) Private IP addresses for a single ENI
ecs.i1.xlarge 4 16.0 2 × 104 0.8 200 No 1 3 10
ecs.i1.2xlarge 8 32.0 2 × 208 1.5 400 No 1 4 10
ecs.i1.3xlarge 12 48.0 2 × 312 2.0 400 No 1 6 10
ecs.i1.4xlarge 16 64.0 2 × 416 3.0 500 No 2 8 20
ecs.i1-c5d1.4xlarge 16 64.0 2 × 1,456 3.0 400 No 2 8 20
ecs.i1.6xlarge 24 96.0 2 × 624 4.5 600 No 2 8 20
ecs.i1.8xlarge 32 128.0 2 × 832 6.0 800 No 3 8 20
ecs.i1-c10d1.8xlarge 32 128.0 2 × 1,456 6.0 800 No 3 8 20
ecs.i1.14xlarge 56 224.0 2 × 1,456 10.0 1,200 No 4 8 20
Note