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.16¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-01c33c8e07496298b
ami-069727100717bf632
Africa (Cape Town)
ami-0e177916b4ab27778
ami-0a6fe118df7298770
Asia Pacific (Mumbai)
ami-09ad14e8c68c527fe
ami-0f1b3792950772936
Europe (Stockholm)
ami-037f1071cf2c9a4ad
ami-09f5f31ac899a92f4
Europe (Paris)
ami-024e1e7c4d04dda55
ami-01466527c73e3bedc
Europe (Milan)
ami-049526512f95c03de
ami-020bc26b3944b3732
Europe (London)
ami-01ce86d145a908d9a
ami-0d9930d35ec50c8dc
Europe (Ireland)
ami-03d0abacf6a980e13
ami-0db6b0d78ecc5eb98
Asia Pacific (Osaka)
ami-0d8fc46c1592a9e89
ami-021726a93694dd52c
Asia Pacific (Seoul)
ami-0f2b08886fe4df53f
ami-04eb5552b02136d9b
Asia Pacific (Tokyo)
ami-02f9fa9affc327ae5
ami-0dbcaef0545ec13e9
Israel (Tel Aviv)
ami-078f314adfa7f6192
ami-00b961961a5a15fd3
Canada (Central)
ami-0722903829f789c2c
ami-0624ba1c30545b4a9
South America (Sao Paulo)
ami-0e58f1b472df9137f
ami-0ce50b390575d4697
Asia Pacific (Hong Kong)
ami-0593160c5838dcce2
ami-0bb3212287f4b65c3
Asia Pacific (Singapore)
ami-0d0fd288388adfb20
ami-0fcf0c57180311f59
Asia Pacific (Sydney)
ami-0fbe4883dc947b6ca
ami-0d14d56a3b14b946f
Europe (Frankfurt)
ami-0752970909056de17
ami-0c06fffeff800fbc4
US East (N. Virginia)
ami-05f9cc8e35810d21a
ami-09ea2bd9c86927b55
US East (Ohio)
ami-08f9b23f6ea6fab21
ami-0feeee6548e612926
US West (N. California)
ami-035084ab9fa0796d8
ami-0df47ff79d73d721c
US West (Oregon)
ami-0702af443990d129f
ami-0b05b434ccd396692
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