Skip to main content
Contact Us
Register
Pure Technical Services

Cloud Block Store Support Matrix for AWS

  1. Last updated
  2. Save as PDF

Currently viewing public documentation. Please login to access the full scope of documentation.

For Azure matrix refer to Cloud Block Store Support Matrix for Azure.

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 

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 based on i3en Virtual Drive

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 based on i3 Virtual Drive

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

Yes

CBS with Purity version 5.3.x 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  
File Service No  
QoS (Fairness) No  
QoS (Limits) Yes  
Purity Run No  
Encryption Yes  
REST APIs Yes  
Controller SW NDU (Purity code) Yes  
Controller HW NDU No
  • Non disruptive upgrade for Purity version (controllers) are fully supported.
  • Non disruptive upgrade from V10 to V20 is supported only by using ActiveCluster.
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

  • Bi-directional supported between two CBS instances in different AZs or regions.
  • Bi-directional supported between CBS instances and FlashArray.
  • Bi-directional supported between two CBS instances cross-clouds.

 

  • AWS network charges may apply for replication across Availability Zones, VPCs, and/or regions.
  • Egress charges may apply for any data sent from Cloud Block Store to FlashArray.

 
ActiveCluster (Synchronous Replication) **

Yes

  • Bi-directional supported between two CBS instances in different AZs.
  • Bi-directional supported between two CBS instances cross-clouds.

 

  • AWS network charges may apply for ActiveCluster configurations across Availability Zones and/or VPCs.
  • For cross-region deployments consider the maximum latency not to exceed 11 ms RTT.
  • For cross-cloud deployments consider the maximum latency not to exceed 11 ms RTT.
  • Minimum Purity version to support cross-cloud on CBS: 6.1.6 or later.
Active-Active Async Replication

Yes

  • CBS as Async target only.
  • V20A-R1 only.
  • Minimum Purity version on FlashArray: 5.3.x or later.
  • Minimum Purity version on CBS: 5.3.x or later.
ActiveDR

Yes

  • Bi-directional supported between two CBS instances in different AZs or regions.
  • Bi-directional supported between CBS instances and FlashArray.
  • Bi-directional supported between two CBS instances cross-clouds.
  • Minimum Purity version on CBS: 6.1.6 or later.
  • ActiveDR between CBS and FlashArray supported on CBS 6.2.x 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

 Limit

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

 Limit
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 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 Pure Cloud Block Store, 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 (CloudSnap) Replication Limits

Description

 Limit

Max # of volume snapshots on an offload target

 10,000
Max # of offload targets configurable per Pure Cloud Block Store 21
Max # of Pure Cloud Block Store configurable per offload target 4

1 Cloud object targets of the same type (2 AWS S3 buckets or 2 Azure blobs).

Host Limits

Description

 Limit

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

LUNs 1-4095 for private or shared connections1

1 Note: Private connections start at 1 and count up. Shared connections start at 255 and count down, then up from 256 if 1-255 are in use.

Host Group Limits

Description

 Limit
Max # of hosts per host group No specific limit beyond max hosts

Max # of LUNs (volumes) per host group

5001

1 Note: Private LUN connections count against host group max LUN limit. See above for LUN ID assignment.

Volume Limits

Description Limit
Max volume size 4PB

//V20AR1 Limits

General Limits 

Description

 Limit

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

 Limit

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 Pure Cloud Block Store,  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 (CloudSnap) Replication Limits

Description

 Limit

Max # of volume snapshots on an offload target

 100,000
Max # of offload targets configurable per Pure Cloud Block Store  21
Max # of Pure Cloud Block Store configurable per offload target 4

1 Cloud object targets of the same type (2 AWS S3 buckets or 2 Azure blobs).

Host Limits

Description

 Limit
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

LUNs 1-4095 for private or shared connections1 

1  Private connections start at 1 and count up. Shared connections start at 255 and count down, then up from 256 if 1-255 are in use.

Host Group Limits

Description

 Limit

Max # of hosts per host group

 No specific limit beyond max hosts

Max # of LUNs (volumes) per host group

5001 

1 Private LUN connections count against host group max LUN limit. See above for LUN ID assignment.

Volume Limits

Description Limit

Max volume size

 4PB