MayaScale on AWS Marketplace
Deploy a 2-node MayaScale active-active storage cluster from the AWS Marketplace using CloudFormation.
Prerequisites
Section titled “Prerequisites”- An AWS account with appropriate IAM permissions
- An existing EC2 key pair for SSH access
- A VPC with subnets in your target availability zone(s)
Step 1: Find MayaScale in AWS Marketplace
Section titled “Step 1: Find MayaScale in AWS Marketplace”- Go to AWS Marketplace
- Search for MayaScale
- Click Continue to Subscribe, then Continue to Configuration
- Select your region and click Continue to Launch
- Choose Launch CloudFormation
Step 2: Configure CloudFormation Stack
Section titled “Step 2: Configure CloudFormation Stack”Deployment Configuration
Section titled “Deployment Configuration”| Parameter | Description | Default |
|---|---|---|
| Cluster Name | Unique cluster identifier | — |
| Performance Policy | Tier selection (basic through ultra, zonal or regional) | zonal-medium |
| Key Pair | EC2 key pair for SSH access | — |
Performance Tiers (AWS)
Section titled “Performance Tiers (AWS)”MayaScale on AWS uses NVMe instance storage families (i3en, i4i):
| Tier | Instance Type | NVMe Devices | Capacity |
|---|---|---|---|
| Basic | i4i.xlarge | 1 | 937 GB |
| Standard | i3en.2xlarge | 2 | 5 TB |
| High | i3en.6xlarge | 4 | 15 TB |
| Ultra | i3en.12xlarge | 8 | 30 TB |
Each tier is available in zonal (same-AZ) and regional (cross-AZ) variants.
Network Configuration
Section titled “Network Configuration”| Parameter | Description | Default |
|---|---|---|
| VPC | Target VPC | Default VPC |
| Availability Zone | Primary AZ | Auto |
Step 3: Deploy
Section titled “Step 3: Deploy”- Review configuration
- Acknowledge IAM capabilities
- Click Create Stack
Deployment takes 5–10 minutes.
Post-Deployment
Section titled “Post-Deployment”Stack Outputs
Section titled “Stack Outputs”Navigate to CloudFormation → Stacks → Outputs:
Node1ExternalIP/Node2ExternalIP— public IPsVIPAddress— primary VIP for client connectionsSSHCommands— ready-to-use SSH commandsPerformancePolicy— selected tierClientVolumes— NVMe-oF connection endpoints
SSH Access
Section titled “SSH Access”ssh -i ~/.ssh/YOUR_KEY.pem ec2-user@<NODE1_PUBLIC_IP>Connect NVMe-oF Client
Section titled “Connect NVMe-oF Client”From a client EC2 instance in the same VPC:
# Install NVMe CLIsudo yum install nvme-cli
# Discover targetsnvme discover -t tcp -a <VIP_ADDRESS> -s 4420
# Connectnvme connect -t tcp \ -n nqn.2019-05.com.zettalane:mayascale-data-node-1 \ -a <VIP_ADDRESS> \ -s 4420
# Verifynvme listWeb UI Access
Section titled “Web UI Access”ssh -L 2020:localhost:2020 -i ~/.ssh/YOUR_KEY.pem ec2-user@<NODE1_PUBLIC_IP># Then open http://localhost:2020What Gets Deployed
Section titled “What Gets Deployed”- 2 EC2 instances with NVMe instance storage
- Security group for SSH and NVMe-oF traffic
- IAM roles and instance profiles
- Placement group (zonal deployments, on-demand only)
- VIP using secondary private IPs for HA
Troubleshooting
Section titled “Troubleshooting”# Cloud-init logstail -f /var/log/cloud-init-output.log
# Check NVMe devicesnvme listlsblk
# Cluster statusmayacli cluster status