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

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-093a96722cdc57590	Node / Cluster	ami-0bbca5a7fcd938d51	Node / Cluster
Africa (Cape Town)	ami-0b9866ab0c3236c45	Node / Cluster	ami-045b722833f16a2ff	Node / Cluster
Asia Pacific (Mumbai)	ami-0ca0f0fe002f9f7b0	Node / Cluster	ami-0cbac0962efd7ff56	Node / Cluster
Europe (Stockholm)	ami-0e33d5ab7b999cc8e	Node / Cluster	ami-0c1cba4d902bc6c6d	Node / Cluster
Europe (Paris)	ami-0dcab24c58cf67be0	Node / Cluster	ami-0a4d1d97160732e63	Node / Cluster
Europe (Milan)	ami-042c419507ae78a31	Node / Cluster	ami-0ab1497499db28587	Node / Cluster
Europe (London)	ami-0edc5a50eb8451181	Node / Cluster	ami-07b0bdf41586329e2	Node / Cluster
Europe (Ireland)	ami-0dea424bb440766b5	Node / Cluster	ami-05efdb4ddecca5a1e	Node / Cluster
Asia Pacific (Osaka)	ami-0c4cbee5b260d970b	Node / Cluster	ami-0c19c001cfa53d77b	Node / Cluster
Asia Pacific (Seoul)	ami-0050bdbc75db47020	Node / Cluster	ami-0720e4cd62a22733a	Node / Cluster
Middle East (Bahrain)	ami-0fbf0c3b1c0c4118b	Node / Cluster	ami-08d15aae9d7e4dc0e	Node / Cluster
Asia Pacific (Tokyo)	ami-0c356d27bab193b91	Node / Cluster	ami-07478ca5829ecb053	Node / Cluster
Israel (Tel Aviv)	ami-081e697ef0dc75a15	Node / Cluster	ami-01e81000d3530fa4e	Node / Cluster
Canada (Central)	ami-0637ccac0f5d1483f	Node / Cluster	ami-058e89a0b252f6203	Node / Cluster
South America (Sao Paulo)	ami-0c3550d52d047cf22	Node / Cluster	ami-0627e2491ac2fff5a	Node / Cluster
Asia Pacific (Hong Kong)	ami-012883d83fc4ece5b	Node / Cluster	ami-0a6b47a7d728ff19e	Node / Cluster
Asia Pacific (Singapore)	ami-00fe63c276b1bee7f	Node / Cluster	ami-069c5890b6239ab75	Node / Cluster
Asia Pacific (Sydney)	ami-0f515d5c114c9ae02	Node / Cluster	ami-0c6ec4a978f829fde	Node / Cluster
Europe (Frankfurt)	ami-09b92b2c44d7cf22c	Node / Cluster	ami-0449f9b11b3b5e620	Node / Cluster
US East (N. Virginia)	ami-0b7f4524d433d0367	Node / Cluster	ami-02ed6a418c39f9671	Node / Cluster
US East (Ohio)	ami-0622753ec92124cb8	Node / Cluster	ami-0bf3dcda003f8c740	Node / Cluster
US West (N. California)	ami-0b499f34a80c0c156	Node / Cluster	ami-0974d52881c00434c	Node / Cluster
US West (Oregon)	ami-0b523977fb02b11a6	Node / Cluster	ami-0344f524b2103f268	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?