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.0¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-03223deb98bbe38a0
ami-065c2c750fda80625
Africa (Cape Town)
ami-018a1f5063e8e7fd9
ami-0135da5978e9a1eea
Asia Pacific (Mumbai)
ami-0df9434cff0cb9426
ami-0beb084b54f6ad040
Europe (Stockholm)
ami-0fa95db56c2cefc1a
ami-0229309b9174ea5d6
Europe (Paris)
ami-03f0af569ebbe79f1
ami-03ae312be5cc5786e
Europe (Milan)
ami-00341f401b1c09e11
ami-0ab2fc7da3f65c5bb
Europe (London)
ami-0121e107e5cc63477
ami-0927d590415095149
Europe (Ireland)
ami-034136a711baf3b69
ami-0d37a1b62504b9063
Asia Pacific (Osaka)
ami-0d423d353a4912db8
ami-0e95eda28ccf7d808
Asia Pacific (Seoul)
ami-041a4e765b920b0c0
ami-0cbf9fa2b63c2a57c
Middle East (Bahrain)
ami-0ab007eafbeb8d80b
ami-0e097172615f6e149
Asia Pacific (Tokyo)
ami-0f20805e02fe1b410
ami-0f84a38fae76b766e
Israel (Tel Aviv)
ami-0735e5d37e9bbdb1d
ami-0ff36dfdcb8182628
Canada (Central)
ami-02f3cb6bb85fdd590
ami-0585a2575e70ec1f6
South America (Sao Paulo)
ami-066e091404f5d6d37
ami-0488c57b0f8c8fb8d
Asia Pacific (Hong Kong)
ami-0ef9175e35fa029b6
ami-02f523ceebed23a45
Asia Pacific (Singapore)
ami-0b049160d98b682ea
ami-0c4aee140a5a2992e
Asia Pacific (Sydney)
ami-02251df1e10035316
ami-04c9a633dde1cb13f
Europe (Frankfurt)
ami-0ed40afd83496c86c
ami-0c66d3c87be662e47
US East (N. Virginia)
ami-0eab7f4f6acc91cc8
ami-0e43c3ca429555d38
US East (Ohio)
ami-0994f13df20bbf52b
ami-0f1cf9cd0b6722adf
US West (N. California)
ami-06513d9adf5966030
ami-057b7e8a479085eeb
US West (Oregon)
ami-0daa9548699471922
ami-0586a342f5b6eb61e
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