Was this page helpful?
Caution
You're viewing documentation for a previous version of ScyllaDB Manual. Switch to the latest stable version.
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.1.15¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-0be9bc9a21bebb378
ami-05873df0f754a8359
Africa (Cape Town)
ami-07a91a71dbeb55070
ami-0a5d4e49104881329
Asia Pacific (Mumbai)
ami-0f62a461cd93bc752
ami-078472e6ed235ce6e
Europe (Stockholm)
ami-09325bd9d5e6d29cd
ami-08e6b47e4b6cca01c
Europe (Paris)
ami-0a7da2db882dc7178
ami-08b0c80438f87f950
Europe (Milan)
ami-0aa46d88f07b2706f
ami-0c88dcc1aad72d434
Europe (London)
ami-091913376819da553
ami-0107d915306c33147
Europe (Ireland)
ami-0af29e4a837ca1fe4
ami-02a29e70c0395924c
Asia Pacific (Osaka)
ami-03d3cf4c14a6e8b6d
ami-0fd54af073d8664ba
Asia Pacific (Seoul)
ami-0b5275e54dc7f6955
ami-078c8e33f73abed3a
Asia Pacific (Tokyo)
ami-0422ed5eec32f439d
ami-06d5091195ed27772
Israel (Tel Aviv)
ami-0ed2f8b716b8aec05
ami-0711833f6b3af80a3
Canada (Central)
ami-0a353228808febabd
ami-00c0a6ef3a8547303
South America (Sao Paulo)
ami-0b8b7dbb3494ec826
ami-034ff0d8a68b9841a
Asia Pacific (Hong Kong)
ami-0fc6655c7bc25ff0c
ami-0f9cea1c7dd506764
Asia Pacific (Singapore)
ami-0198ab3ff9f7e0a1e
ami-0fd3e47875306349b
Asia Pacific (Sydney)
ami-051a1e2d2a9688b5b
ami-0b76cdb68ffa00bd0
Europe (Frankfurt)
ami-03d29a116ea5645e3
ami-09238786d3f345681
US East (N. Virginia)
ami-0c0d2a52abe3f494c
ami-0987ca9b63684cdfc
US East (Ohio)
ami-0e856f9a67face25d
ami-096a1cb5b259bed41
US West (N. California)
ami-001a77544d24434ca
ami-0d6da9adc2aee302e
US West (Oregon)
ami-0a5f8b95a3292ee9f
ami-0c0ada0f25ac9046e
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