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.3 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.3.6¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-0173b97bf7467e0fd
ami-0ff51a58b027cc36a
Africa (Cape Town)
ami-045c5a394ae4e9c02
ami-0583fc0e84c2adb29
Asia Pacific (Mumbai)
ami-0b3d131ba035cb0c3
ami-099f5eaf8bd8f4f4a
Europe (Stockholm)
ami-03dc720d16d44e26e
ami-09e1445732c9f6185
Europe (Paris)
ami-0c0a7b54979e8a4dd
ami-0766dcb37d0a85058
Europe (Milan)
ami-06df2533e06ab870e
ami-07ae56fb1cc30204e
Europe (London)
ami-0600c06b5476caed4
ami-0c4b9a5e39081c076
Europe (Ireland)
ami-0ff5189f1ab5d1346
ami-09f6e6d8eda989d0d
Asia Pacific (Osaka)
ami-068145b18b4cddcab
ami-068ec0dc0993a4cbd
Asia Pacific (Seoul)
ami-0e68e0cbaed173193
ami-01355d41c3dfd7ffd
Asia Pacific (Tokyo)
ami-0af9129649191964c
ami-053302ac92994b866
Israel (Tel Aviv)
ami-0459579f6e8830c34
ami-02ce1a744debe5939
Canada (Central)
ami-0d254f548d11f38cb
ami-015c649d6f9f88a13
South America (Sao Paulo)
ami-0257158d95eaff18b
ami-0e5fc74016d9bb23c
Asia Pacific (Hong Kong)
ami-01b0dd08b330a3813
ami-04e6de00c1d8a80de
Asia Pacific (Singapore)
ami-08e29b420d392ff41
ami-0f8e3ea86501f365a
Asia Pacific (Sydney)
ami-03164758bb93e1839
ami-016d9f60908345eea
Europe (Frankfurt)
ami-01a61107a73ccc008
ami-0fca3437d4dd6e3f9
US East (N. Virginia)
ami-092e9afcd9fc7f2d9
ami-0d07cacf564f05bdc
US East (Ohio)
ami-01b07e5ee886047f4
ami-08d35fc2953d2d3fb
US West (N. California)
ami-0b7e7b55e5f7abb3b
ami-0d7587d587016d328
US West (Oregon)
ami-075825edaf31b67c0
ami-03261bf3bc591d991
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