Scylla on Amazon EC2

Choose AMI

Amazon EC2 AMIs

Note that the Scylla AMIs will not work without an attached drive(s) for XFS.

US East (Virginia) us-east-1 ami-ad07e0d0 Scylla 2.0.3 AMI
US West (California) us-west-1 ami-c01e16a0 Scylla 2.0.3 AMI
US West 2 (Oregon) us-west-2 ami-6b9e1213 Scylla 2.0.3 AMI
EU West 1 (Ireland) eu-west-1 ami-9f730ce6 Scylla 2.0.3 AMI

Choose an Instance Type

For a production system, instances with fast network and large SSD are recommended. The following instances are pre-tuned in the Scylla AMI and recommended for high performance:
  • i3 [i3.xlarge .. i3.8xlarge]
  • i2 [i2.xlarge … i2.8xlarge]
Other instance types will work, but with lesser permanence. If you do choose such a type, make sure to run scylla_io_setup. For running Scylla 1.7 or older on i3 instance see here.

Configure Instance Details

  • 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.
Option Description
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.
seeds Optional. An ip address of a node in an existing cluster. This will instruct Scylla to join an existing cluster. The “clustername” option must match that of the existing cluster.
stop-services Optional. Do not start Scylla service on the nodes
--clustername test-cluster
--totalnodes 3

EC2 Configure Instance Details Capture

Add Storage

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.

Tag Instance

Configure Security Group

Make sure all Scylla Ports are open.


Launch! You now have a running Scylla cluster on EC2.

To connect to the servers, use the username centos.

ssh -i your-key-pair.pem centos@ec2-public-ip

Default file paths:

  • scylla.yaml at /etc/scylla/scylla.yaml
  • data at /var/lib/scylla/

To check that the Scylla server and the JMX component are running, run nodetool.

nodetool status

Note: This Scylla AMI does not support automatic multi-zone deployment.


It is highly recommended to have a Scylla monitoring stack in place. For more on how to setup Scylla monitoring with Grafana here


Scylla servers set up using this method have the system configuration covered on System Configuration Guide already applied. See the guide for a complete reference on settings used.

Apache®, Apache Cassandra®, are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. No endorsement by The Apache Software Foundation is implied by the use of these marks.