Was this page helpful?
Launch ScyllaDB 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.
2025.2.0¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-025d0b777a6ae5c84
ami-01c12e7139f32be8c
Africa (Cape Town)
ami-06155ee04ea02d874
ami-0cc7ecab696c25978
Asia Pacific (Mumbai)
ami-015eeeeefe611b6ca
ami-0c2fcc4fe2a52b42a
Europe (Stockholm)
ami-0d9768d3a5caaf40c
ami-062e06d2051829f2d
Europe (Paris)
ami-0cfe1ceef9fbcb8ea
ami-02ca54812a88e6717
Europe (Milan)
ami-0268e47bb17065d54
ami-0030c7b920018a7cf
Europe (London)
ami-09c3f727a901dcd82
ami-0439d4474177e4e47
Europe (Ireland)
ami-09bd6100532483d15
ami-09989b20fd8d15be7
Asia Pacific (Osaka)
ami-05eb00fd683756ebb
ami-07d7e50ab79ae3e56
Asia Pacific (Seoul)
ami-0bb5f6d14efc11015
ami-0f1c8b6590dbf7da0
Middle East (Bahrain)
ami-072d09730fe14a396
ami-00ccb3b855662356a
Asia Pacific (Tokyo)
ami-0dc213698ff9964ac
ami-008fe20fcbec0eeea
Israel (Tel Aviv)
ami-0378d6d4b9058d52e
ami-0129ed027b6e4e7ac
Canada (Central)
ami-0f566a82acc9645b8
ami-0095f54f8e4dbe03c
South America (Sao Paulo)
ami-0336224c27ce56327
ami-0bf002bf4498c05a4
Asia Pacific (Hong Kong)
ami-01eab370b8df98c9e
ami-05609258850b3ec20
Asia Pacific (Singapore)
ami-01a5d3f2fc16e70e9
ami-0f311dea69682275a
Asia Pacific (Sydney)
ami-08d9c8934f09cb507
ami-05851dc253ef6ddd1
Europe (Frankfurt)
ami-02e76adaefa062242
ami-0be771ed7c55296c9
Asia Pacific (Jakarta)
ami-02dafd0ce41336866
ami-0a5fbb6b6cd124079
US East (N. Virginia)
ami-08680b94b47e8fb23
ami-08cf9760056568b4d
US East (Ohio)
ami-006d8544301190b4b
ami-0eb03439149d0c390
US West (N. California)
ami-0b6a0c9724756b74d
ami-013609c8d159818be
US West (Oregon)
ami-008dfdaffced6cddc
ami-0a3294a5127759ed2
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
seeds
parameter - 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-ip
The default file paths:
The
scylla.yaml
file:/etc/scylla/scylla.yaml
Data:
/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