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.9¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-0a149235025de0b57
ami-0a6543531f5581885
Africa (Cape Town)
ami-051cc939c51a1746d
ami-0d1ff147dfb66aca2
Asia Pacific (Mumbai)
ami-056dc7f4977e349dc
ami-023e178be710ed07a
Europe (Stockholm)
ami-003cfe8caf6d181de
ami-0f7053c53505bb742
Europe (Paris)
ami-0904218138fa8e2fa
ami-014b0f00631a31336
Europe (Milan)
ami-06315a4db867209c2
ami-0a5828e47d29f0e99
Europe (London)
ami-0fe489af4ac21beed
ami-063c93b83acb27b25
Europe (Ireland)
ami-0db699a97c0a3cdc0
ami-07ca463929506eec6
Asia Pacific (Osaka)
ami-0acf013b82f774cea
ami-0b3de57af052ed015
Asia Pacific (Seoul)
ami-047743fc6190321da
ami-0ff138c44526399de
Asia Pacific (Tokyo)
ami-0e8f5e637e4efa673
ami-0385181b15ded0572
Israel (Tel Aviv)
ami-01ba8d78d320e501f
ami-0a4cb4bfccca49d41
Canada (Central)
ami-0294878f524a9cc98
ami-06fe4cf248d970892
South America (Sao Paulo)
ami-016ce3262b54ccd27
ami-065d2b800b555619c
Asia Pacific (Hong Kong)
ami-0f763e61473b22f81
ami-0c760f1a3d91c1c34
Asia Pacific (Singapore)
ami-08cc4827f0e1b2eb9
ami-0e3d40b6a683db108
Asia Pacific (Sydney)
ami-0bbf9d678a33aac4b
ami-099986411554e5564
Europe (Frankfurt)
ami-0d0a6398e16d44785
ami-08a624f10a7bc7263
US East (N. Virginia)
ami-0e8cc13693133a35e
ami-03d155637f3d87198
US East (Ohio)
ami-00c64f49f71e08534
ami-05bb58c24ab4db634
US West (N. California)
ami-084675ab86b8fc198
ami-0e074e6adfa7c95fa
US West (Oregon)
ami-06a1245d97862958b
ami-00c3594ade597473d
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