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.3¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-02abad134918c40b0
ami-06e1af9a8f90bfc87
Africa (Cape Town)
ami-07c2822b7b8cb6640
ami-0d7b7a8e56df312d9
Asia Pacific (Mumbai)
ami-05b61a2b7d2c15e67
ami-04976670340b31fd0
Europe (Stockholm)
ami-0d8f9fb9ab8daaea8
ami-0563b269e87ebdea0
Europe (Paris)
ami-088434976f9fb2505
ami-05a8d801663fb7f68
Europe (Milan)
ami-03f58bfb02feea612
ami-0f5fd04c23a44d5e3
Europe (London)
ami-0cd8b402afdc34a19
ami-03d46336ebf5e0183
Europe (Ireland)
ami-0123fb67536291266
ami-0554474e95cd5d37f
Asia Pacific (Osaka)
ami-0552657fb1c85f9ff
ami-0c3487720140ff60d
Asia Pacific (Seoul)
ami-09acf1d49a2220c77
ami-07f2084d0100758b6
Asia Pacific (Tokyo)
ami-02f07a6f80fb23abd
ami-0d83da5bb09c08ef4
Israel (Tel Aviv)
ami-01650d8b93c83ebca
ami-035df0ceeae8a23ae
Canada (Central)
ami-040663f100edb8786
ami-0cc8b72fa11a8dbe0
South America (Sao Paulo)
ami-0becbbe1a1ccc31c2
ami-0e3242ce6d7e75495
Asia Pacific (Hong Kong)
ami-0e85ab11b16961c8d
ami-08262b4c6c0e19c88
Asia Pacific (Singapore)
ami-0ac67cda91714caa9
ami-014cc13b2f3d30a4f
Asia Pacific (Sydney)
ami-0655aae6a15b904c8
ami-081570e33e8dfdb85
Europe (Frankfurt)
ami-0be74749af90b7e8d
ami-0392481e58f7024c5
US East (N. Virginia)
ami-09031ff3ab228b6c9
ami-0e44dfce7ce4f6321
US East (Ohio)
ami-0200673631a5d8d91
ami-0b37a5bb7860b4451
US West (N. California)
ami-093f0851437f0cabc
ami-002bfbc2be5fa86c3
US West (Oregon)
ami-0f96bd742eb52104b
ami-0d62aa9eb80e8a94e
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