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.13¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-0a1ee6aaaaaf29ee2
ami-0d22c6a2a9a0483a9
Africa (Cape Town)
ami-05ae922eabf53c53f
ami-07e0f82bf63ff23e0
Asia Pacific (Mumbai)
ami-06c16b2e04b0029a2
ami-0a10af1c2e0b96b40
Europe (Stockholm)
ami-02786e86182f1eff9
ami-01a57babfdac9bcd5
Europe (Paris)
ami-089355065128d2b81
ami-0bd49d809417fff33
Europe (Milan)
ami-0f7e66038f48a30aa
ami-0c8ad2c3b0a6acf1f
Europe (London)
ami-05ba1384ce2313c60
ami-0d2a97cb9070c1f65
Europe (Ireland)
ami-0168d6d6a70b8cd76
ami-0dd309578bffe9437
Asia Pacific (Osaka)
ami-0e3ebbdb08de63424
ami-09768642d213c03ec
Asia Pacific (Seoul)
ami-02ac429c7a1a37f58
ami-0a00795489e9832b7
Asia Pacific (Tokyo)
ami-0bdc51ea0fb7da6f9
ami-0727edaf2ae2f88a1
Israel (Tel Aviv)
ami-03c2f943289caed04
ami-0fd74b06b00e00840
Canada (Central)
ami-03c565b689649df63
ami-0f679a3e23d641456
South America (Sao Paulo)
ami-0bfd6712e0cf34fd7
ami-0b91b3ab25d61ea22
Asia Pacific (Hong Kong)
ami-08e108c2d85394d1f
ami-018351991e1ed976d
Asia Pacific (Singapore)
ami-0d2b0767024151755
ami-09140f8c1d1b19114
Asia Pacific (Sydney)
ami-089f0757a2c705dfe
ami-0a3ebc3186f8ffacf
Europe (Frankfurt)
ami-0a7e8621cd5c5133b
ami-08aca0ce95e9ef080
US East (N. Virginia)
ami-01aa1f008941a129f
ami-0724099320d2de166
US East (Ohio)
ami-033c41950d954df09
ami-0b9d471b77e1d7997
US West (N. California)
ami-099d744e7f6c3c0d6
ami-0146d58654e29716a
US West (Oregon)
ami-0203e6736849ac8a9
ami-0770d30f877595b5e
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