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

Launch ScyllaDB 2026.1 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.

2026.1.1¶

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-093109bf6546ef4f8	Node / Cluster	ami-076197f1a00f5a5df	Node / Cluster
Africa (Cape Town)	ami-0325595631b46f404	Node / Cluster	ami-0254e50482842d5c7	Node / Cluster
Asia Pacific (Mumbai)	ami-06ddcaa108616c039	Node / Cluster	ami-0a76db8f358e5cb00	Node / Cluster
Europe (Stockholm)	ami-010041b9a88256735	Node / Cluster	ami-029501e3dfe021e79	Node / Cluster
Europe (Paris)	ami-019cfa47468a0e837	Node / Cluster	ami-06eb9ef3ca5141ca4	Node / Cluster
Europe (Milan)	ami-0a57ac155385482e3	Node / Cluster	ami-0ae568ccf445459f6	Node / Cluster
Europe (London)	ami-06085519be6a2dc72	Node / Cluster	ami-0a53ff06aa1faa18d	Node / Cluster
Europe (Ireland)	ami-087fc2dc8ced7046b	Node / Cluster	ami-08c83ec6bbd40d283	Node / Cluster
Asia Pacific (Osaka)	ami-02b78f170872cc2e6	Node / Cluster	ami-0b1dda60ba86c3fc6	Node / Cluster
Asia Pacific (Seoul)	ami-07026edba65835be0	Node / Cluster	ami-05d36700bcae1dbdf	Node / Cluster
Asia Pacific (Tokyo)	ami-01a34de3a54d87029	Node / Cluster	ami-07da7cc2dadf32a51	Node / Cluster
Israel (Tel Aviv)	ami-0bfb62d1b148b490f	Node / Cluster	ami-0e04915bfb0eabb18	Node / Cluster
Canada (Central)	ami-0cd1cdbac6a1bbbca	Node / Cluster	ami-05f91bb2709e2913f	Node / Cluster
South America (Sao Paulo)	ami-05632c2227f07c20e	Node / Cluster	ami-0074d63bee8514603	Node / Cluster
Asia Pacific (Hong Kong)	ami-04cda5ccd8c907f74	Node / Cluster	ami-09cab5d6541a7621c	Node / Cluster
Asia Pacific (Singapore)	ami-07e55311e1bbce999	Node / Cluster	ami-060377221c464ec7e	Node / Cluster
Asia Pacific (Sydney)	ami-081b022a440cd59d7	Node / Cluster	ami-008a6bfdeeb123500	Node / Cluster
Europe (Frankfurt)	ami-0936d3db32c5f4f41	Node / Cluster	ami-0c8acaf2138defe39	Node / Cluster
US East (N. Virginia)	ami-0688dd24b95e1e179	Node / Cluster	ami-04e4f51549157a213	Node / Cluster
US East (Ohio)	ami-018979a16ac4afecc	Node / Cluster	ami-0ce513b857a88b0b3	Node / Cluster
US West (N. California)	ami-0453c049bd879d312	Node / Cluster	ami-04ef36ae7597af7d1	Node / Cluster
US West (Oregon)	ami-0b5caa55dbf4a7bd9	Node / Cluster	ami-04e4e3e4de387ea06	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?