Deploying on AWS (Marketplace)
QuasarSDS can be deployed on AWS with a CloudFormation template that creates a 3-node cluster (RF3) inside your existing VPC.
What the template creates
- 3 EC2 instances running k3s (one server and two agents), all acting as storage nodes.
- Additional network interfaces per role (peer, replication and, at the highest tier, backup).
- An S3 Gateway VPC Endpoint for backups, with no NAT Gateway required.
- An instance IAM role with access through SSM Session Manager.
The template does not create a VPC, subnets or route tables: it only asks for 3 subnets, ideally in 3 different availability zones so that RF3 survives the loss of an entire AZ.
Tiers by instance type
| Tier | Instance types | Use |
|---|---|---|
| 0 — Evaluation | t3.medium, c5.large | Testing. No performance guarantee. |
| 1 — Production | t3.large, m5.large, i4i.large | Recommended minimum for real workloads. |
| 2 — Recommended | t3.xlarge, m5.xlarge, i4i.xlarge | Full network separation by role. |
The right SPDK image for each instance type's CPU is selected automatically.
Main parameters
| Parameter | Description |
|---|---|
VpcId, SubnetId0-2, RouteTableIds | Existing network where the cluster is deployed. |
InstanceType | Determines the tier (table above). |
SshAllowedCidr | Range allowed to connect over SSH. Intentionally has no default. |