ScyllaDB Docs ScyllaDB Manual Getting Started Install ScyllaDB Launch ScyllaDB on AWS

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.4.1¶

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-08a4a81c6b1f74b5c	Node / Cluster	ami-0c5eb3e21b7dc06bf	Node / Cluster
Africa (Cape Town)	ami-00f7e70cad2482c48	Node / Cluster	ami-07bda85d24474496a	Node / Cluster
Asia Pacific (Mumbai)	ami-01256fbfc0caa2dd0	Node / Cluster	ami-0811972f0ae768814	Node / Cluster
Europe (Stockholm)	ami-01312307502f4e78d	Node / Cluster	ami-092985e1b9553292f	Node / Cluster
Europe (Paris)	ami-02a25d2475e992acf	Node / Cluster	ami-0f91ad9b5de73e43e	Node / Cluster
Europe (Milan)	ami-0368d26bbc5c3537d	Node / Cluster	ami-09c6ffce42b43c053	Node / Cluster
Europe (London)	ami-0a3acb87b13e73bc5	Node / Cluster	ami-04c4f99fa2d84a7e2	Node / Cluster
Europe (Ireland)	ami-05c067b036edcddf7	Node / Cluster	ami-075086140e4ae05ff	Node / Cluster
Asia Pacific (Osaka)	ami-0447045143ab4cc7d	Node / Cluster	ami-07341c631e27c9c10	Node / Cluster
Asia Pacific (Seoul)	ami-0e0b342f4cab0bd28	Node / Cluster	ami-070f654ea6c9ee529	Node / Cluster
Middle East (Bahrain)	ami-0c7023ced35cab79b	Node / Cluster	ami-008d84b05f1d64f6c	Node / Cluster
Asia Pacific (Tokyo)	ami-0555f0bfc41b088ca	Node / Cluster	ami-0cd44fb3f3bdf6f8f	Node / Cluster
Israel (Tel Aviv)	ami-06c02fa637445366c	Node / Cluster	ami-0535888bb9270bfee	Node / Cluster
Canada (Central)	ami-039a1812f87b2a2f4	Node / Cluster	ami-0cde2dbefd521c0d7	Node / Cluster
South America (Sao Paulo)	ami-0f4cfcd5c058796c7	Node / Cluster	ami-012877a3b886f39ac	Node / Cluster
Asia Pacific (Hong Kong)	ami-0259cb643c1536ce8	Node / Cluster	ami-081590c42b6a316fa	Node / Cluster
Asia Pacific (Singapore)	ami-087bd20534a6c831d	Node / Cluster	ami-033f4876d4c9ec021	Node / Cluster
Asia Pacific (Sydney)	ami-02bc1580dd008ff7e	Node / Cluster	ami-03feec947889db893	Node / Cluster
Europe (Frankfurt)	ami-00596ca33ab99da3b	Node / Cluster	ami-05ca2f800e2dd74da	Node / Cluster
US East (N. Virginia)	ami-0a640fc95b49376b7	Node / Cluster	ami-046b35257e13bee65	Node / Cluster
US East (Ohio)	ami-0f47c227dbbaf322b	Node / Cluster	ami-0c51798a69d802895	Node / Cluster
US West (N. California)	ami-08cec6e61cf19fc05	Node / Cluster	ami-08926d334174477dd	Node / Cluster
US West (Oregon)	ami-0215c23b101ec8b2b	Node / Cluster	ami-0d0240def2773f8da	Node / Cluster

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¶

Configure ScyllaDB
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

Was this page helpful?