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.4¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-01ca557917826ffec
ami-0e8a37d009db168f2
Africa (Cape Town)
ami-0097ec86c81ca690b
ami-0dd53f17836ddc348
Asia Pacific (Mumbai)
ami-00d7b969d347d9f73
ami-03f9ecf2f5a16ca47
Europe (Stockholm)
ami-03cce60a4c5463ee8
ami-0a3603618d8e19877
Europe (Paris)
ami-01d91a4f380dd411d
ami-02a68245e5e49a5fb
Europe (Milan)
ami-0e65d76ac7b1856b6
ami-06a0afdf5ce8f8597
Europe (London)
ami-0da4acc2a058eecaa
ami-0b2274a9594b2fc66
Europe (Ireland)
ami-04ff1135f87566613
ami-0dd60e3b43a9386df
Asia Pacific (Osaka)
ami-0460ef6acedd3c27f
ami-0055e382a4b993e43
Asia Pacific (Seoul)
ami-003597b58c9f7b6d9
ami-0ba73653c9fdd8107
Asia Pacific (Tokyo)
ami-09affb3b306bdbd9d
ami-08944caa0de765cad
Israel (Tel Aviv)
ami-00946c08634218c50
ami-055994997e18722fb
Canada (Central)
ami-0e53dd6e536c86de9
ami-0b8269388f5ef18e1
South America (Sao Paulo)
ami-0d8c7f1222c7f9d36
ami-03c7d7b00c5bcedb6
Asia Pacific (Hong Kong)
ami-017dfe16fc88c8bc8
ami-09edec3f53f661397
Asia Pacific (Singapore)
ami-0d324de7a60ab5934
ami-0250ce25b4d2cae32
Asia Pacific (Sydney)
ami-081ecb82d911eb73e
ami-0080bacc5b8c20ca1
Europe (Frankfurt)
ami-0ece4830bbecb2451
ami-0f3c5678262d3a37d
US East (N. Virginia)
ami-08f977929696f0a3d
ami-013666987cd0175d3
US East (Ohio)
ami-07b6dcf45bfea8f45
ami-0bf6a80894e70f5a9
US West (N. California)
ami-07de08d54b8081ecd
ami-01be045482f65dd6f
US West (Oregon)
ami-0720c77091a240a21
ami-0cccd8a9c2d96f014
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