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.7¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-0f61af7f7e321e15b
ami-0566fe3ea0f1591dd
Africa (Cape Town)
ami-0eef7af728000d8ce
ami-00b68984d577e8305
Asia Pacific (Mumbai)
ami-0c3eb07f4157889b3
ami-0afcbd690211ebedd
Europe (Stockholm)
ami-0568b83bcdb39780e
ami-0ce8f33a26955a703
Europe (Paris)
ami-0234f5fc3c09f5dd5
ami-076f3b0946dacdc78
Europe (Milan)
ami-022b738ffab5181a3
ami-0d5cd3f167e32fc01
Europe (London)
ami-0d8b6fc866ddb79f6
ami-009117d01281f107e
Europe (Ireland)
ami-00fcc62b9143be2ac
ami-0461d878cbf14b000
Asia Pacific (Osaka)
ami-065d8f1faa8951045
ami-0cdef77c2a3afdfc0
Asia Pacific (Seoul)
ami-055a2fcf2d6fc0250
ami-0518d39ec79e7e18b
Asia Pacific (Tokyo)
ami-0d50276faa02c5657
ami-0e30c9b637467a03f
Israel (Tel Aviv)
ami-07d2c0e6ad716bc80
ami-07f4f9e9d34e40cb2
Canada (Central)
ami-079f5fa7bb4dd33e0
ami-05f75758b4643b49f
South America (Sao Paulo)
ami-0ae2b39c073fd25b8
ami-00df8880069ebfb7d
Asia Pacific (Hong Kong)
ami-0855b274d2f6deaff
ami-02aba8ab5c8a9323f
Asia Pacific (Singapore)
ami-043b2838da8e6b2a1
ami-011cbec059a70df46
Asia Pacific (Sydney)
ami-09804b6bfc89b7d26
ami-055ecc2011b26b71c
Europe (Frankfurt)
ami-02eb4ade5ab71898d
ami-09489bb18ed0f93c6
US East (N. Virginia)
ami-00130003c54887021
ami-0f9ff705ac0bfd63f
US East (Ohio)
ami-0c545aff8f3517617
ami-071105eeb2dd58611
US West (N. California)
ami-018d63f5199738416
ami-03a9524c00d18ea8f
US West (Oregon)
ami-03657ac474e0d0b2f
ami-08dc8fe89cbaa9c4f
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