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.10¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-065e05c74475f4228
ami-097fd862c4a9f2b9f
Africa (Cape Town)
ami-0c944ab571c95f407
ami-003c1ba5c63fafbab
Asia Pacific (Mumbai)
ami-0d37bd8448d46d6da
ami-0ae5593fadaebb473
Europe (Stockholm)
ami-0c368cde5416b622b
ami-07aa3b65845deac8d
Europe (Paris)
ami-0a08bd2b3f414bc1e
ami-000f2c3da23e2dd99
Europe (Milan)
ami-083640673cc95fab5
ami-02ea140ca0bb2b775
Europe (London)
ami-0fe7c7f033cca054d
ami-0c1eb480bcd550779
Europe (Ireland)
ami-0f795862b47cfb83f
ami-061b7da4d89f31762
Asia Pacific (Osaka)
ami-018c67ba9c9e8b362
ami-0cbc5491c0fcd1253
Asia Pacific (Seoul)
ami-08e9d5db71a2856e7
ami-03ec83da95d6e5525
Asia Pacific (Tokyo)
ami-00e58d8fd9dec5841
ami-08b47e47fed4901e4
Israel (Tel Aviv)
ami-07fba79fad9c69f62
ami-06e292eda53a639e9
Canada (Central)
ami-00c13ef888c0754b0
ami-061fb0d05a273395c
South America (Sao Paulo)
ami-0ea8646a1a9f8790f
ami-0dcb10e62ca21921f
Asia Pacific (Hong Kong)
ami-0084b33069ef9e969
ami-0d9cea3be5a02930a
Asia Pacific (Singapore)
ami-08478ddd620221788
ami-03eada86d080d66e4
Asia Pacific (Sydney)
ami-02c0445d4dda19da9
ami-0b532f3e4bfccae8a
Europe (Frankfurt)
ami-039200e16e4045d35
ami-0f2d82b23559025d3
US East (N. Virginia)
ami-022d607c6b77831d3
ami-090589606dd14b718
US East (Ohio)
ami-081dd2ed4246364dd
ami-0ccf92ff93eca06fb
US West (N. California)
ami-0c2a5de4a3e6f7341
ami-0650730285eae2adc
US West (Oregon)
ami-03fb6ebba60ae7955
ami-04c187058198e741b
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