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.5¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-05366fde5efef83ef
ami-0d580dc97b51a6cb5
Africa (Cape Town)
ami-0ff943ed564677478
ami-0e918b8d637b9c4f4
Asia Pacific (Mumbai)
ami-09baae35fad50edd9
ami-09a54ebcb7a206ec6
Europe (Stockholm)
ami-07e4a2f94c4291d64
ami-03c0712c6d72bf816
Europe (Paris)
ami-08288d7a57286c957
ami-08f8516f27ce9feb7
Europe (Milan)
ami-09c6336d666fe46df
ami-071403ed33cfcdfb2
Europe (London)
ami-0edfd6ee0adb365b8
ami-0f7e63f2356f953a7
Europe (Ireland)
ami-0152917d202ad52f6
ami-014421eabc759080f
Asia Pacific (Osaka)
ami-072e7df094781d8e7
ami-0d3b4ab477829eb64
Asia Pacific (Seoul)
ami-0fb5ad96b653e18b7
ami-0c3f10818e740417c
Asia Pacific (Tokyo)
ami-0537144170999dc4f
ami-0a18ca9ddb75b7f0d
Israel (Tel Aviv)
ami-09daf872ba6fcb56d
ami-091f24bca4d5cff68
Canada (Central)
ami-03938d75810fec31f
ami-037ecebb1fec6a4a1
South America (Sao Paulo)
ami-069d14064c679b065
ami-006d89a54c6c43aad
Asia Pacific (Hong Kong)
ami-0606b43538ceff526
ami-009bf3902d58ac4ac
Asia Pacific (Singapore)
ami-0d8992f3c0e5b3ba8
ami-0a6b2cc46c4c889be
Asia Pacific (Sydney)
ami-01a12fbd4b53f142e
ami-00fe0fa1745211a2c
Europe (Frankfurt)
ami-0e865208dd8691881
ami-0512a4b024b0c62b0
US East (N. Virginia)
ami-059beae625f8d348b
ami-061c88eefba08914e
US East (Ohio)
ami-09e9afc80bdc77f23
ami-031ff063c6ea8db87
US West (N. California)
ami-06c7f966a13505a1c
ami-06c599da768650865
US West (Oregon)
ami-0c87eae2bdbb36a86
ami-077404c6143fed1dd
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