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.15¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-077f4ab06adff6deb
ami-0746ec252d7a1ad88
Africa (Cape Town)
ami-0e4f2ed982f8d579e
ami-02bcc31d266cd6597
Asia Pacific (Mumbai)
ami-03b58ce72048004af
ami-0d2222e1097d55ad8
Europe (Stockholm)
ami-08f88ec9fe2cd5b36
ami-0a1347e9a99ce6f28
Europe (Paris)
ami-0530fd9e9d3124531
ami-0cf699182e1fe236b
Europe (Milan)
ami-09fcb940e9c02c3d7
ami-0c4647e3ea50a918a
Europe (London)
ami-0eba407292249f418
ami-05048115f6bd26f80
Europe (Ireland)
ami-0a1d8520f053c1c07
ami-0b125c5a1a279e701
Asia Pacific (Osaka)
ami-0622d09cefd23e834
ami-072e19f79a9962d16
Asia Pacific (Seoul)
ami-04dbe8acddd1c5d8d
ami-0f33a613b7386c0bd
Asia Pacific (Tokyo)
ami-08b025569e703c490
ami-0afd36f9acc48c380
Israel (Tel Aviv)
ami-0133941cef06c7466
ami-01b7d5c3a44f48f5c
Canada (Central)
ami-0149c61f32cc042ad
ami-0da61f8eac3cc7518
South America (Sao Paulo)
ami-041a37a146aef9838
ami-0f0f8c940308a12a2
Asia Pacific (Hong Kong)
ami-0e1bba495fe069eb1
ami-01cdbbc5d2fe4f791
Asia Pacific (Singapore)
ami-0aec5cceb728f8b1a
ami-07ebf8cdd2f668f49
Asia Pacific (Sydney)
ami-02e367ca41557d658
ami-080df99c476a5f790
Europe (Frankfurt)
ami-0830f43cca9f9ac27
ami-096aa81862bff8e4e
US East (N. Virginia)
ami-0322d79e1fdaace6d
ami-01e09c1895bb3f2b9
US East (Ohio)
ami-055b97eeab08499ea
ami-00ef1e6a3285edd73
US West (N. California)
ami-04826e03d924db85c
ami-0a67b12ce107e2776
US West (Oregon)
ami-03949d773ff61ff3f
ami-0197e61ddaff985ab
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