Supported configurations in AWS
Suggest changes
PDFs
Several Cloud Volumes ONTAP configurations are supported in AWS.
Supported number of nodes
Cloud Volumes ONTAP is available in AWS as a single node system and as a high-availability (HA) pair of nodes for fault tolerance and nondisruptive operations.
Upgrading a single node system to an HA pair is not supported. If you want to switch between a single node system and an HA pair, then you need to deploy a new system and replicate data from the existing system to the new system.
Supported storage
Cloud Volumes ONTAP supports several types of EBS disks, and S3 object storage for data tiering. The maximum storage capacity is determined by the license that you choose.
Storage support by license
Each license supports a different maximum system capacity. The maximum system capacity includes disk-based storage plus object storage used for data tiering. NetApp doesn’t support exceeding this limit.
| Freemium | Capacity-based license | |
|---|---|---|
Maximum system capacity |
500 GiB |
2 PiB 2 |
Supported disk types |
|
|
Cold data tiering to S3 |
Supported |
|
Notes:
-
For an HA pair, the capacity limit is for the entire HA pair. It's not per node. For example, if you use the Premium license, you can have up to 368 TiB of capacity between both nodes.
-
For some configurations, disk limits prevent you from reaching the capacity limit by using disks alone. In those cases, you can reach the capacity limit by tiering inactive data to object storage. For information about disk limits, refer to storage limits.
-
Enhanced write performance is enabled when using SSDs with all Cloud Volumes ONTAP configurations.
-
Tiering data to object storage is not recommended when using Throughput Optimized HDDs (st1).
-
AWS Local Zones only support the General Purpose SSD (gp2) disk type.
| PAYGO Explore | PAYGO Standard | PAYGO Premium | Node-based BYOL | |
|---|---|---|---|---|
Maximum system capacity |
2 TiB |
10 TiB |
368 TiB 2 |
368 TiB per license 2 |
Supported disk types |
|
|||
Cold data tiering to S3 |
Not supported |
Supported |
||
Notes:
-
For an HA pair, the capacity limit is for the entire HA pair. It's not per node. For example, if you use the Premium license, you can have up to 368 TiB of capacity between both nodes.
-
For some configurations, disk limits prevent you from reaching the capacity limit by using disks alone. In those cases, you can reach the capacity limit by tiering inactive data to object storage. For information about disk limits, refer to storage limits.
-
Enhanced write performance is enabled when using SSDs with all Cloud Volumes ONTAP configurations, except for PAYGO Explore.
-
Tiering data to object storage is not recommended when using Throughput Optimized HDDs (st1).
-
AWS Local Zones only support the General Purpose SSD (gp2) disk type.
Supported disk sizes
In AWS, an aggregate can contain up to 6 disks that are all the same size. But if you have a configuration that supports the Amazon EBS Elastic Volumes feature, then an aggregate can contain up to 8 disks. Learn more about support for Elastic Volumes
| General Purpose SSDs (gp3 and gp2) | Provisioned IOPS SSDs (io1) | Throughput Optimized HDDs (st1) |
|---|---|---|
|
|
|
Supported EC2 compute
Each Cloud Volumes ONTAP license supports different EC2 instance types. For your convenience, the table below shows the vCPU, RAM, and bandwidth for each supported instance type. You should refer to AWS for the latest and complete details about EC2 instance types.
Cloud Volumes ONTAP can run on either a Reserved or On-demand EC2 instance. Solutions that use other instance types aren't supported.
The bandwidths shown in the table below match the documented AWS limits for each instance type. These limits don't completely align with what Cloud Volumes ONTAP can provide. For the expected performance, refer to NetApp Technical Report 4383: Performance Characterization of Cloud Volumes ONTAP in Amazon Web Services with Application Workloads.
| License | Supported instance | vCPU | RAM | Flash Cache 1 | Network bandwidth (Gbps) | EBS bandwidth (Mbps) | High write speed 2 |
|---|---|---|---|---|---|---|---|
Explore or any other license |
m5.xlarge 6 |
4 |
16 |
Not supported |
Up to 10 |
Up to 4,750 |
Supported (single node only) |
Standard or any other license |
r5.xlarge 6 |
4 |
32 |
Not supported |
Up to 10 |
Up to 4,750 |
Supported (single node only) |
m5a.2xlarge |
8 |
32 |
Not supported |
Up to 10 |
Up to 2,880 |
Supported |
|
m5.2xlarge 6 |
8 |
32 |
Not supported |
Up to 10 |
Up to 4,750 |
Supported |
|
Premium or any other license |
m5n.2xlarge |
8 |
32 |
Not supported |
Up to 25 |
Up to 4,750 |
Supported |
r5.2xlarge 6 |
8 |
64 |
Not supported |
Up to 10 |
Up to 4,750 |
Supported |
|
r5d.2xlarge |
8 |
64 |
Supported |
Up to 10 |
Up to 4,750 |
Supported |
|
c5d.4xlarge 6 |
16 |
32 |
Supported |
Up to 10 |
4,570 |
Supported |
|
m5.4xlarge 6 |
16 |
64 |
Not supported |
Up to 10 |
4,750 |
Supported |
|
m5dn.4xlarge |
16 |
64 |
Supported |
Up to 25 |
4,750 |
Supported |
|
m5d.8xlarge |
32 |
128 |
Supported |
10 |
6,800 |
Supported |
|
r5.8xlarge |
32 |
256 |
Not supported |
10 |
6,800 |
Supported |
|
c5.9xlarge |
36 |
72 |
Not supported |
10 |
9,500 |
Supported |
|
c5d.9xlarge |
36 |
72 |
Supported |
10 |
9,500 |
Supported |
|
c5n.9xlarge |
36 |
96 |
Not supported |
50 |
9,500 |
Supported |
|
c5a.12xlarge |
48 |
96 |
Not supported |
12 |
4,750 |
Supported |
|
c5.18xlarge |
64 4 |
144 |
Not supported |
25 |
19,000 |
Supported |
|
c5d.18xlarge |
64 4 |
144 |
Supported |
25 |
19,000 |
Supported |
|
m5d.12xlarge |
48 |
192 |
Supported |
12 |
9,500 |
Supported |
|
m5dn.12xlarge |
48 |
192 |
Supported |
50 |
9,500 |
Supported |
|
c5n.18xlarge |
64 4 |
192 |
Not supported |
100 |
19,000 |
Supported |
|
m5a.16xlarge |
64 |
256 |
Not supported |
12 |
9,500 |
Supported |
|
m5.16xlarge |
64 |
256 |
Not supported |
20 |
13,600 |
Supported |
|
r5.12xlarge 3 |
48 |
384 |
Not supported |
10 |
9,500 |
Supported |
|
m5dn.24xlarge |
64 4 |
384 |
Supported |
100 |
19,000 |
Supported |
|
m6id.32xlarge |
64 4 |
512 |
Supported |
50 |
40,000 |
Supported |
-
Some instance types include local NVMe storage, which Cloud Volumes ONTAP uses as Flash Cache. Flash Cache speeds access to data through real-time intelligent caching of recently read user data and NetApp metadata. It's effective for random read-intensive workloads, including databases, email, and file services. Compression must be disabled on all volumes to take advantage of the Flash Cache performance improvements. Learn more about Flash Cache.
-
Cloud Volumes ONTAP supports high write speed with most instance types when using an HA pair. High write speed is supported with all instance types when using a single node system. Learn more about choosing a write speed.
-
The r5.12xlarge instance type has a known limitation with supportability. If a node unexpectedly reboots due to a panic, the system might not collect core files used to troubleshoot and root cause the problem. The customer accepts the risks and limited support terms and bears all support responsibility if this condition occurs. This limitation affects newly deployed HA pairs and HA pairs upgraded from 9.8. The limitation does not affect newly deployed single node systems.
-
While these EC2 instance types support more than 64 vCPUs, Cloud Volumes ONTAP only supports up to 64 vCPUs.
-
When you choose an EC2 instance type, you can specify whether it is a shared instance or a dedicated instance.
-
AWS Local Zones are supported in the following EC2 instance type families with sizes xlarge to 4xlarge: M5, C5, C5d, R5, and R5d. You should refer to AWS for the latest and complete details about supported EC2 instance types in Local Zones.
High write speed isn't supported with these instance types in AWS Local Zones.
Supported regions
For AWS region support, see Cloud Volumes Global Regions.