Was this page helpful?
Caution
You're viewing documentation for an unstable 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.2¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-0d77113dc74cc075a
ami-063788272a06bd959
Africa (Cape Town)
ami-03efe8f33d20f1230
ami-0518a5f8ef1e7a69b
Asia Pacific (Mumbai)
ami-00444fdac9be0e773
ami-0cf2b5d8c5370f77d
Europe (Stockholm)
ami-0ee769403d553461f
ami-0b71a46ccc22e71c9
Europe (Paris)
ami-0ed1d0f613e5a3b9c
ami-02ee3001265634b20
Europe (Milan)
ami-0c9e5693263ce9c2f
ami-0e2a413b3863d590e
Europe (London)
ami-047ba31c661acc585
ami-095a346fd9e84646a
Europe (Ireland)
ami-0498263b8e68c5b06
ami-0bff376139017b563
Asia Pacific (Osaka)
ami-06a9f4c913bd13e7d
ami-0757d00c3d8f8b513
Asia Pacific (Seoul)
ami-05603e8a413d669a3
ami-080f2420a1848d2bd
Asia Pacific (Tokyo)
ami-02b748c68242e5b39
ami-08b1febe96680db9d
Israel (Tel Aviv)
ami-0cfbc235c658b36a9
ami-07f9b1bfd12fbed09
Canada (Central)
ami-089eadf53c1f9c5eb
ami-04b82f967963fea51
South America (Sao Paulo)
ami-09dbe29b1bdbccd3f
ami-0ce8fd269bf93213f
Asia Pacific (Hong Kong)
ami-0d33822511961b597
ami-080540c0b55ac8ef0
Asia Pacific (Singapore)
ami-017d7a83a399dd5de
ami-036f89146de8fbb7e
Asia Pacific (Sydney)
ami-07db9912e67335ae3
ami-02f4d3e1ad7aa7a9c
Europe (Frankfurt)
ami-04e3f08c1f3c94b4f
ami-0400cdd88d16d868a
US East (N. Virginia)
ami-0ca8f5bc3c8b7e44b
ami-0874abe1445b71d3c
US East (Ohio)
ami-00c075f6c9d365fb9
ami-064fad19700fb926f
US West (N. California)
ami-0a27c4f7021062238
ami-027e327c88bf93f42
US West (Oregon)
ami-0d40a43a14d1b0f58
ami-0d524cf661f969ded
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