Cloud Block Store Support Matrix for AWS
Cloud Block Store Models and Capacity Points
For more detailed information about all the underlying components, see the Cloud Block Store Architecture & Underlying Resources article.
It is not currently possible to upgrade from a V10 to a V20 (or downgrade) without a data migration. When choosing a platform consider potential future use and that a switch requires data movement. Platform upgrades are being considered for a future release.
CBS//V10-R1 - For arrays launched with Purity version 5.X and 6.X
Model | Usable | Effective (4:1) |
CBS //V10A-R1 Base Config |
6.9 TiB (7.6 TB) |
27.6 TiB (30.3 TB) |
CBS //V10A-R1 After Capacity NDU |
13.8 TiB (15.2 TB) |
55.2 TiB (60.7 TB) |
CBS//V20-R1 - For arrays launched with Purity version 6.X
Model | Usable | Effective (4:1) |
CBS //V20A-R1 Base Config |
27.2 TiB (29.9 TB) |
108.6 TiB (119.5 TB) |
CBS //V20A-R1 After Capacity NDU |
57.5 TiB (63.3 TB) |
230.2 TiB (253.1 TB) |
CBS//V20-R1 - For arrays launched with Purity version 5.X
Model | Usable | Effective (4:1) |
CBS //V20A-R1 Base Config |
13.8 TiB (15.2 TB) |
55.2 TiB (60 TB) |
CBS //V20A-R1 After Capacity NDU #1 |
27.6 TiB (30.4 TB) |
110.4 TiB (121.4 TB) |
CBS //V20A-R1 After Capacity NDU #2 |
55.2 (TiB) 60.8 (TB) |
220.8 TiB (242.8 TB) |
Supported Capabilities and Features
Feature/Capability | Support | Notes |
Nesting CloudFormation template | No | Cloud Block Store is deployed using CloudFormation. Pure provides customers with a CloudFormation (CF) template yaml file. Cloud Block Store must be deployed using its own standalone CloudFormation template. It is important that customers do not nest the Cloud Block Store CloudFormation template in other CloudFormation templates as this can lead to unexpected configuration issues over time. |
Terraform Deployment | Yes | See Using Terraform to Deploy Cloud Block Store in AWS for details. |
Shut down or Stop (Suspend/Resume) | Yes |
Stopping or Shutting down Cloud Block Store is supported by following the proper steps provided in here: How to Suspend/Resume a Cloud Block Store array in AWS Do not shut down underlying CBS ec2 resources. |
Cloud Block Store termination/deletion |
Support Driven: v5.3.0.aws0, 5.3.0.aws1, 5.3.0.aws2 Customer Driven: v5.3.3.aws0+ |
CBS with Purity version v5.3.0.aws0, 5.3.0.aws1, and 5.3.0.aws2 requires Pure Support in order to delete a CBS instance. CBS with Purity version 5.3.3.aws0 and higher can be deleted by customers. See CBS Deployment Guide for steps to terminate/delete a CBS instance. |
Host ports | 2 (iSCSI) | One per controller |
Replication ports | 2 | One per controller |
Management ports | 2 | One per controller |
Deduplication | Yes | |
Compression | Yes | |
Thin Provisioning | Yes | |
Snapshots | Yes | |
CloudSnap creation | Yes | |
CloudSnap restore | Yes | |
Snap to NFS | No | |
Safemode | Yes | |
QoS (Fairness) | No | |
QoS (Limits) | Yes | |
Purity Run | No | |
WFS | No | |
Encryption | Yes | |
REST APIs | Yes | |
Controller SW NDU (Purity code) | Yes | |
Controller HW NDU | No |
|
Capacity NDU * | Yes | Support Driven via CLI commands |
Pure1 | Yes | |
Pure1 Meta (Workload Planner) | No | |
VM Analytics | N/A | No VMware Cloud support for CBS |
VMware Cloud | No | |
Changing Network IP or subnets | No | This is an AWS limitation |
Boot from CBS | No | This is an AWS limitation. EC2 instances are only allowed to boot from native AWS storage. |
Replication Features | Support | Notes |
Async Replication
|
Yes
|
|
ActiveCluster (Synchronous Replication) ** |
Yes
|
|
Active-Active Async Replication |
Yes
|
|
ActiveDR |
Yes
|
Minimum Purity version on CBS: 6.1.6 or later. |
* Capacity upgrade is supported by adding additional virtual drives, seven at a time. However, capacity upgrade in-place from i3.2xlarge to i3.4xlarge is not supported.
** Cloud Block Store in an ActiveCluster configuration is not supported in Oregon if using with Pure1 Mediator. Customers who want to deploy Cloud Block Store with ActiveCluster in Oregon must use the On-Premises Mediator.
//V10AR1 Limits
General Limits
Description |
5.3.x |
---|---|
Max # of volumes |
500 |
Max # of hosts |
300 (6.1.7+) |
Max # of sessions | 2400 |
Max # of host groups |
50 |
Snapshots and Asynchronous Replication Limits
Description |
5.3.x |
---|---|
Max # of volume snapshots per array | 10,000 |
Max # of pgroups per array1 | 250 |
Max # of pgroup snapshots per array1 | 5000 |
Max # of remote connected arrays | 1 |
Minimum configurable replication frequency2 |
5 minutes |
1 Example for pgroup and snapshot limits: If you create a pgroup containing 100 volumes and then create a single pgroup snapshot for that pgroup then the following would be counted against each maximum:
- 1 pgroup consumed from the array-wide maximum number of pgroups
- 1 pgroup snapshot consumed from the array-wide pgroup snapshot maximum
- 100 volume snapshots consumed from the array-wide volume snapshot maximum
Note: In cases where a pgroup snapshot request will result in more volume snapshots than are supported by the FlashArray, the pgroup snapshot request and/or scheduled pgroup snapshot will fail.
2 This is the minimum configurable replication frequency. Replication is a background process and priority is given to front-end workload. Maintaining the configured replication frequency depends on several factors such as the front-end workload on the array, the amount of data reduction, the amount of logical address space being replicated, and the available replication bandwidth.
Snapshot Offload (NFS/Cloud) Replication Limits
Description |
5.3.x |
---|---|
Max # of volume snapshots on an offload target |
10,000 |
Max # of offload targets configurable per FlashArray | 1 |
Max # of FlashArrays configurable per offload target | 4 |
Host Limits
Description |
5.3.x |
---|---|
Max # of LUNs (volumes) per host |
500 |
Max # of private LUNs connected per host (LUNs not connected to host groups) | 500 |
LUN IDs assigned for LUN connections |
|
Host Group Limits
Description |
5.3.x |
---|---|
Max # of hosts per host group | No specific limit beyond max hosts |
Max # of LUNs (volumes) per host group |
500 Note: Private LUN connections count against host group max LUN limit. See above for LUN ID assignment. |
Volume Limits
Description | 5.3.x |
---|---|
Max volume size | 4PB |
//V20AR1 Limits
General Limits
Description |
5.3.x |
---|---|
Max # of volumes |
1000 |
Max # of hosts |
300 (6.1.7+) |
Max # of sessions | 4800 |
Max # of host groups |
100 |
Snapshot and Asynchronous Replication Limits
Description |
5.3.x |
---|---|
Max # of volume snapshots per array1 |
20,000 |
Max # of pgroups per array1 | 250 |
Max # of pgroup snapshots per array1 | 5000 |
Max # of remote connected arrays | 4 |
Minimum configurable replication frequency2 |
5 minutes |
1 Example for pgroup and snapshot limits: If you create a pgroup containing 100 volumes and then create a single pgroup snapshot for that pgroup then the following would be counted against each maximum:
- 1 pgroup consumed from the array-wide maximum number of pgroups
- 1 pgroup snapshot consumed from the array-wide pgroup snapshot maximum
- 100 volume snapshots consumed from the array-wide volume snapshot maximum
Note: In cases where a pgroup snapshot request will result in more volume snapshots than are supported by the FlashArray, the pgroup snapshot request and/or scheduled pgroup snapshot will fail.
2 This is the minimum configurable replication frequency. Replication is a background process and priority is given to front-end workload. Maintaining the configured replication frequency depends on several factors such as the front-end workload on the array, the amount of data reduction, the amount of logical address space being replicated, and the available replication bandwidth.
Snapshot Offload (NFS/Cloud) Replication Limits
Description |
5.3.x |
---|---|
Max # of volume snapshots on an offload target |
100,000 |
Max # of offload targets configurable per FlashArray | 1 |
Max # of FlashArrays configurable per offload target | 4 |
Host Limits
Description |
5.3.x |
---|---|
Max # of LUNs (volumes) per host | 500 |
Max # of private LUNs connected per host (LUNs not connected to host groups) | 500 |
LUN IDs assigned for LUN connections |
|
Host Group Limits
Description |
5.3.x |
---|---|
Max # of hosts per host group |
No specific limit beyond max hosts |
Max # of LUNs (volumes) per host group |
500 Note: Private LUN connections count against host group max LUN limit. See above for LUN ID assignment. |
Volume Limits
Description | 5.3.x |
---|---|
Max volume size |
4PB |