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.10¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-05faa473b9f6d0aa1
ami-0ae1e9cceefef3766
Africa (Cape Town)
ami-0da344ca3f8b3c90a
ami-028b4deda161d4c5d
Asia Pacific (Mumbai)
ami-0af43650b3b59937b
ami-0146dcb67d684b5ea
Europe (Stockholm)
ami-0c300b44f2506c627
ami-0d78e6966dfe2d165
Europe (Paris)
ami-009759fec8e5d2a29
ami-0f17538cdc767c655
Europe (Milan)
ami-09fdbeffb62a2af90
ami-05eb4f5afb25b632e
Europe (London)
ami-0be06f74f8490d75b
ami-0f0fe8c642b12b987
Europe (Ireland)
ami-09b0e427fa626adfd
ami-0bd5d5ad78379797a
Asia Pacific (Osaka)
ami-04ee249df8b1ecb8d
ami-0723a73af7c8aaa41
Asia Pacific (Seoul)
ami-00f11ade0fc806631
ami-09baad74db8c97c40
Asia Pacific (Tokyo)
ami-0975451e0db5414a1
ami-069a9b851d8e779a9
Israel (Tel Aviv)
ami-0ca8e3025eee67ddb
ami-00e52e5050d4c0c7e
Canada (Central)
ami-05fcac23b29721b09
ami-032ebf152303bee43
South America (Sao Paulo)
ami-03b277d87964503f3
ami-094ff0a502f265d0e
Asia Pacific (Hong Kong)
ami-00afba1113efd8e0d
ami-0211dbdec04c1068b
Asia Pacific (Singapore)
ami-019a8d6b8998d3143
ami-090ce58b3dbb43078
Asia Pacific (Sydney)
ami-06c4069c36473e843
ami-0c079cf3526de0aac
Europe (Frankfurt)
ami-045ccc5eb91b86cd5
ami-02f78a08de408f4cd
US East (N. Virginia)
ami-0d5bc56421aee77a7
ami-0a0757b895a4b9ef6
US East (Ohio)
ami-0aa7f280942c4928d
ami-06a00d800671a2ebd
US West (N. California)
ami-036b9d8c08426556b
ami-038c16b5ccf2e8820
US West (Oregon)
ami-0530f2cecb321e93a
ami-000151a1a0ab186d5
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