Was this page helpful?
Caution
You're viewing documentation for a previous version of ScyllaDB Manual. Switch to the latest stable version.
Launch ScyllaDB 2026.1 on AWS¶
This article will guide you through self-managed ScyllaDB deployment on AWS. For a fully-managed deployment of ScyllaDB as-a-service, see ScyllaDB Cloud documentation.
Launching Instances from ScyllaDB AMI¶
Choose your region, and click the Node link to open the EC2 instance creation wizard.
The following table shows the latest patch release. See AWS Images for earlier releases.
2026.1.14¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-020aebd2cf0cc0bb6
ami-0327929296b885865
Africa (Cape Town)
ami-0972cac56ca1c9445
ami-04ec578b1da6aea09
Asia Pacific (Mumbai)
ami-0e64a7f04df03bc11
ami-003fe08a864ac6792
Europe (Stockholm)
ami-08c41e1d3870f9ca4
ami-0d9f8d921baecef41
Europe (Paris)
ami-00e50fdefa3ee3d9c
ami-0c3ad85de6d8fac9b
Europe (Milan)
ami-095003f748810f9ef
ami-0948e86d8295848a3
Europe (London)
ami-0c4358fe69260a08a
ami-0b2467a4dd5964d6f
Europe (Ireland)
ami-031a6d587150bdb9e
ami-063729f5ede21debf
Asia Pacific (Osaka)
ami-0f5fec25fe1330575
ami-08dc9c250e2f17888
Asia Pacific (Seoul)
ami-0240c8b09687342c5
ami-0ff9cbfc949ee12ba
Asia Pacific (Tokyo)
ami-0617b80b06e3d0668
ami-0e5bf0865144014f1
Israel (Tel Aviv)
ami-02db10dda8b24dbaa
ami-08b26a6097459b006
Canada (Central)
ami-0303e66adefb62dc2
ami-0590e2d6df207e1a3
South America (Sao Paulo)
ami-0b27c35f0e44a7e20
ami-0887698b67e119637
Asia Pacific (Hong Kong)
ami-0da2a3d88c7be2c49
ami-09efadbb082836bf2
Asia Pacific (Singapore)
ami-05e9a59f69013dede
ami-06a6b71b85ea7a470
Asia Pacific (Sydney)
ami-08a67d0bf26fd9273
ami-05dc1b00b6f808071
Europe (Frankfurt)
ami-07c9aae4d9339bc50
ami-01498af7b2a2d686f
US East (N. Virginia)
ami-0aa103f8dcbec4b39
ami-04e3241fa8c7b44e0
US East (Ohio)
ami-03dfabe9fcedbf7da
ami-0fc98cc6010caf5b3
US West (N. California)
ami-0ad0a291d749c54bc
ami-0b279830ba59a92d5
US West (Oregon)
ami-0ceeaa67bc746c937
ami-09cf9ef2189ead728
Choose the instance type. See Cloud Instance Recommendations for AWS for the list of recommended instances.
Other instance types will work, but with lesser performance. If you choose an instance type other than the recommended ones, make sure to run the scylla_setup script.
Configure your instance details.
Number of instances – If you are launching more than one instance, make sure to correctly set the IP of the first instance with the
seedsparameter - either in the User Data (see below) or after launch.Network – Configure the network settings.
Select your VPC.
Configure the security group. Ensure that all ScyllaDB ports are open.
Advanced Details> User Data – Here, you can add ScyllaDB configuration options in the JSON format. See scylla.yaml for information about supported options.
The following example shows a configuration using the most popular options.
cluster_name- The name of the cluster.seed_provider- The IP of the first node. New nodes will use the IP of this seed node to connect to the cluster and learn the cluster topology and state. See ScyllaDB Seed Nodes.post_configuration_script- A base64 encoded bash script that will be executed after the configuration is completed.start_scylla_on_first_boot- Starts ScyllaDB once the configuration is completed.
Example:
{ "scylla_yaml": { "cluster_name": "test-cluster", "seed_provider": [{"class_name": "org.apache.cassandra.locator.SimpleSeedProvider", "parameters": [{"seeds": "10.0.219.209"}]}], }, "post_configuration_script": "#! /bin/bash\nyum install cloud-init-cfn", "start_scylla_on_first_boot": true }
For full documentation of ScyllaDB AMI user data, see the ScyllaDB Image documentation.
Add storage.
ScyllaDB AMI requires XFS to work. You must attach at least one drive for ScyllaDB to use as XFS for the data directory. When attaching more than one drive, the AMI setup will install RAID0 on all of them.
The ScyllaDB AMI requires at least two instance store volumes. The ScyllaDB data directory will be formatted with XFS when the instance first boots. ScyllaDB will fail to start if only one volume is configured.
Tag your instance.
Click Launch Cluster. You now have a running ScyllaDB cluster on EC2.
Connect to the servers using the username
scyllaadm.ssh -i your-key-pair.pem scyllaadm@ec2-public-ipThe default file paths:
The
scylla.yamlfile:/etc/scylla/scylla.yamlData:
/var/lib/scylla/
To check that the ScyllaDB server is running, run:
nodetool status
Next Steps¶
Manage your clusters with ScyllaDB Manager
Monitor your cluster and data with ScyllaDB Monitoring
Get familiar with ScyllaDB’s command line reference guide.
Learn about ScyllaDB at ScyllaDB University