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.2 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.2.11¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-0a7457c5e938ace10
ami-0328b68d592f59bdd
Africa (Cape Town)
ami-0cf0677e6c714a7f1
ami-04e723e13e9c27152
Asia Pacific (Mumbai)
ami-05faf281aac89a48f
ami-0167f0df3b11f294c
Europe (Stockholm)
ami-006554781ee693890
ami-015bc571e6ae01fd5
Europe (Paris)
ami-0c209793edefaa698
ami-0efbeb33b906e2c23
Europe (Milan)
ami-01cff51a219f23e40
ami-0aff2f38c9d296b0a
Europe (London)
ami-0097e7ecb8a2a74ce
ami-0f70ccddaa8c8514f
Europe (Ireland)
ami-0ab22226e2fdfb7e8
ami-04cbe212557973373
Asia Pacific (Osaka)
ami-0bdf9965c07bf049e
ami-0cb5810ace263b4fa
Asia Pacific (Seoul)
ami-04811a6b4c64e73ee
ami-0ce60bc7e1194da5d
Asia Pacific (Tokyo)
ami-093a33c3c7cee80bc
ami-0b5a8933b08b0e6cb
Israel (Tel Aviv)
ami-0b9e7ec95cc919974
ami-0671fdb1c0bf37126
Canada (Central)
ami-078ff4347dae9e2fa
ami-0d4c2c6157b47a02f
South America (Sao Paulo)
ami-02f6968df9cdc9b4d
ami-0034389d436b4d595
Asia Pacific (Hong Kong)
ami-0bfa7c26492b1b6c7
ami-02c0fc68af8eea9d0
Asia Pacific (Singapore)
ami-054a91613e2780b05
ami-0c943322496d0aeec
Asia Pacific (Sydney)
ami-0eceaaa0a5b9954fe
ami-047a7ec75f2855aea
Europe (Frankfurt)
ami-00f1725e6f7235ab2
ami-0c1270f1e80a8f2fe
US East (N. Virginia)
ami-07325f06a722fe9ac
ami-03c862e19d9e38d03
US East (Ohio)
ami-04463166e35909efc
ami-00500e888be07c7e3
US West (N. California)
ami-034923f24781707ae
ami-044c3216c2c6e2a9a
US West (Oregon)
ami-00b09d7f857650f6a
ami-040c2080df389b355
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