Getting Started with Scylla on Amazon EC2¶
For a production system, instances with fast network and large SSD are recommended. The following instances are pretuned in the Scylla AMI and recommended for high performance:
- i2 [i2.xlarge … i2.8xlarge]
- m3 [m3.medium .. m3. 2xlarge]
- c3 [c3.large .. c3.8xlarge]
Other instance types will work, but with lesser permanence. If you do choose such a type, make sure to run scylla_io_setup.
- Number of instances - base on your cluster planning
- Network - Select “Launch into EC2-Classic”, or your own VPC.
- Advanced Details - Open and add the following options (as text) to the User Data section.
|clustername||Required. The name of the cluster.|
|totalnodes||Required. The number of nodes you are adding to cluster. Use the same value as the “Number of instances” above.|
--clustername test-cluster --totalnodes 3
EC2 Configure Instance Details Capture
Scylla AMI require XFS to work. You Must attach at least one drive for Scylla to use as XFS for the data directory. When attaching more than one drive, AMI setup will install RAID0 on all of them.
The Scylla AMI requires at least two instance store volumes. The Scylla data directory will be formatted with XFS when the instance first boots. Scylla will fail to start if only one volume is configured.
Launch! You now have a running Scylla cluster on EC2.
To connect to the servers, use the username
ssh -i your-key-pair.pem centos@ec2-public-ip
Default file paths:
- scylla.yaml at
- data at
To check that the Scylla server and the JMX component are running, run
Note: This Scylla AMI does not support automatic multi-zone deployment.