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.5¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-05ea74f8b140b875e
ami-05883a8a085adc6f2
Africa (Cape Town)
ami-0c7bcc78358490592
ami-0aa9767de9f27b742
Asia Pacific (Mumbai)
ami-0a7cdfb581f845d08
ami-0d3c8de976f9640ff
Europe (Stockholm)
ami-0c289317d249bb240
ami-0c47bbae1bde93e9b
Europe (Paris)
ami-0e8f194fcc114614b
ami-0c2f17311ab8f92b0
Europe (Milan)
ami-0f8c635359dee13af
ami-05d452da1b690c0bb
Europe (London)
ami-07ab85cf4351b3bbf
ami-0afb824e601fb9b5b
Europe (Ireland)
ami-005f49447730de6d9
ami-0242d7476d3d718c4
Asia Pacific (Osaka)
ami-0bdbed32a1d49cd2b
ami-0ba23a97624141d52
Asia Pacific (Seoul)
ami-0ef830b3a0e1ec879
ami-0a9e80977f880fd1a
Asia Pacific (Tokyo)
ami-0b1b84ca2b7c34a1e
ami-0e80383b129f7d90b
Israel (Tel Aviv)
ami-0a226838c8c1da398
ami-0a0a7d04205a75fe5
Canada (Central)
ami-00255a9893f19dc0e
ami-0790cc950dccbc322
South America (Sao Paulo)
ami-0bfedf9c090096d09
ami-0d6eaeb6cd0dc9f8f
Asia Pacific (Hong Kong)
ami-04ddc06946a796986
ami-0d075d38a0edc8e27
Asia Pacific (Singapore)
ami-016182cd466dd4696
ami-09ec0d911022a7508
Asia Pacific (Sydney)
ami-0c13c866fba293e16
ami-09661049da3ac82ea
Europe (Frankfurt)
ami-0cb70a183f2b71f02
ami-0a9f9f93e8d9cca98
US East (N. Virginia)
ami-067ca3ec659a75d3b
ami-0ec587e9a36724b41
US East (Ohio)
ami-04ba2825b3cc81715
ami-04c7958b245f0594f
US West (N. California)
ami-0b888dbb7b3f6e868
ami-02e62ab2863b500e7
US West (Oregon)
ami-0e828c91f5007c035
ami-06cb4a7b042c17752
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