This section explains the main functionality of Cloud Native Qumulo on AWS (CNQ), shows the reference architecture, and lists the known limits. In addition, it provides an overview of the two-phase deployment.
What is Cloud Native Qumulo on AWS?
CNQ on AWS is a self-managed AWS VPC deployment that provisions EC2 instances and uses AWS infrastructure for a Qumulo file system, which allows the disaggregation of persistent storage from compute resources. You can deploy CNQ on AWS by using AWS CloudFormation or Terraform.
CNQ on AWS provides the same multi-protocol support, interfaces, and functionality as Qumulo on premises.
Reference Architecture
Overview of Deploying CNQ on AWS
This section outlines the process of configuring and deploying CNQ on AWS.
-
Create persistent storage by using S3 buckets.
-
Deploy cluster compute and cache resources.
-
Perform post-deployment actions.
-
Optimize your deployment.
CNQ on AWS Limits
This section lists the CNQ on AWS limits.
-
24-Node Clusters (CloudFormation): Although the Cloud Native Qumulo architecture can scale to a high number of nodes, CloudFormation deployments of CNQ on AWS are limited to a maximum of 24 nodes. For more information, contact the Qumulo Care team.
-
Elastic Block Storage (EBS) gp3 EBS Volume Optimization: When you use configurations with IOPS or throughput values greater than the defaults of 125 IOPS and 3000 MiB/s, you must ensure that your EBS volumes complete their optimization when you run performance tasks.
Tip
Because all volumes for a Qumulo cluster are tagged with the same deployment name, you can use the deployment name to filter volumes in the AWS Console. -
Amazon S3 Bucket Warm-Up: Because CNQ on AWS uses S3 buckets for backing storage, the S3 buckets are subject to throttling prior to partition scale-up.