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.2 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.2.3¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-013c65199d63861ce
ami-056cb01d387f0b6f6
Africa (Cape Town)
ami-0191645e2dd0b5580
ami-03683502ddb0e37af
Asia Pacific (Mumbai)
ami-0da49b75ddbd4f339
ami-0978790928aaa1a33
Europe (Stockholm)
ami-0110d36c7995b7eb0
ami-0c8f34da1cc7ba59e
Europe (Paris)
ami-0d6b53546c43a3ac6
ami-0ff3def641f6ff15e
Europe (Milan)
ami-0f5d4267e039dbf09
ami-0b1cff9bdbfd88d51
Europe (London)
ami-0e3230d2398bac8f2
ami-08e7716f616c4d33f
Europe (Ireland)
ami-0d56ab0d60dd581c1
ami-0c69ea41e2703e975
Asia Pacific (Osaka)
ami-0b5ff32894ec783f6
ami-04d4c49b2f7784073
Asia Pacific (Seoul)
ami-0af35d310cc983ccd
ami-01095b6aa0692a0d9
Asia Pacific (Tokyo)
ami-062f53a20da48822c
ami-0c1dd65745b7a75c8
Israel (Tel Aviv)
ami-083a60e04228f9533
ami-0a8c9823eaee5025a
Canada (Central)
ami-01e66bbf5d17db4af
ami-07981f82113dd1156
South America (Sao Paulo)
ami-07868bfe9dea32971
ami-041b23e1e6c5bf3f0
Asia Pacific (Hong Kong)
ami-0151660e2a9e0fb9d
ami-001a96100da2cc227
Asia Pacific (Singapore)
ami-09cdbc19041a47c21
ami-04af6ea31b47c3384
Asia Pacific (Sydney)
ami-0fb6822c233dccaec
ami-073be181c5e6c0d97
Europe (Frankfurt)
ami-0eb920a760771452a
ami-08461cd5737b60a74
US East (N. Virginia)
ami-04506ffe4aaa52525
ami-009069b6e5b514774
US East (Ohio)
ami-0f9c05dffe1596a9b
ami-075eb943b499400dc
US West (N. California)
ami-017060b0f97f755c6
ami-01f7f1d379dd4d242
US West (Oregon)
ami-03fd1a53bcacd749f
ami-079b6c16aa980b049
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