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.12¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-09525f039a15f236c
ami-0f6665ae1f9b5a3db
Africa (Cape Town)
ami-06f5e02633ecc4c5e
ami-081d7f5040512f2b4
Asia Pacific (Mumbai)
ami-021cb4c3e13911ad1
ami-055a8e67a43548910
Europe (Stockholm)
ami-0b289f05fd5573169
ami-0d58cc0c3ba8a4558
Europe (Paris)
ami-0b7daf0586146543e
ami-06e9b2636514ef390
Europe (Milan)
ami-04372e43e27969283
ami-0f4ce47cff745ec21
Europe (London)
ami-0625d5eac6279537b
ami-02a41fc1d841f6604
Europe (Ireland)
ami-0f5374181c54fde46
ami-033d9734413f8096c
Asia Pacific (Osaka)
ami-080f01af7b137e36b
ami-07aeb617d8124843f
Asia Pacific (Seoul)
ami-077851f92e2b00d94
ami-0ad1f537a21eeb35e
Asia Pacific (Tokyo)
ami-002601dd48468457f
ami-0bf87f2f81d9ade87
Israel (Tel Aviv)
ami-0d64ba455e5f4d386
ami-07cab7f8fe9741951
Canada (Central)
ami-05e351dd746955f62
ami-083bea89bb05b2260
South America (Sao Paulo)
ami-0ef7ade83b7f69c53
ami-05d9e5730918a54a3
Asia Pacific (Hong Kong)
ami-0aeeb0116139234a1
ami-0a0ed414aeb96478b
Asia Pacific (Singapore)
ami-071ecda60784a40c3
ami-01acd4c6c06a79db3
Asia Pacific (Sydney)
ami-0ea8e4a9b31435dae
ami-068e8a0ccacbf0aa9
Europe (Frankfurt)
ami-0dfa6c1644f841595
ami-0a8ed08c658928600
US East (N. Virginia)
ami-0d41941aace23f56a
ami-01df5d38d4e29cad9
US East (Ohio)
ami-049f4bf2e2a89b541
ami-0e6a7a14ad1384242
US West (N. California)
ami-00f2aaf6e3ee487d7
ami-03d90c710084211fd
US West (Oregon)
ami-065df1cb2d8369a38
ami-012a4f2d672afae21
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