Launch ScyllaDB 2026.3 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.3.1¶

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-04f932de2726dde0c	Node / Cluster	ami-05be5d07e04c87097	Node / Cluster
Africa (Cape Town)	ami-001f4ed9b104e471b	Node / Cluster	ami-0c976ca28276bac5d	Node / Cluster
Asia Pacific (Mumbai)	ami-0e18d9981d78a718a	Node / Cluster	ami-0972a568cc0e5c783	Node / Cluster
Europe (Stockholm)	ami-0e8843352db9b7009	Node / Cluster	ami-01a2a9721716752bd	Node / Cluster
Europe (Paris)	ami-046965df3be642637	Node / Cluster	ami-06c64312dda135c27	Node / Cluster
Europe (Milan)	ami-07b23bd285f475fff	Node / Cluster	ami-0198a5d89e4bbf542	Node / Cluster
Europe (London)	ami-0906cb2b26505bede	Node / Cluster	ami-00f56e4aa4befb268	Node / Cluster
Europe (Ireland)	ami-06a012eede2682823	Node / Cluster	ami-08089c983641d991e	Node / Cluster
Asia Pacific (Osaka)	ami-0a2bbd1d471cf8128	Node / Cluster	ami-0f67187711b9dfe38	Node / Cluster
Asia Pacific (Seoul)	ami-072bb1413f7ea4740	Node / Cluster	ami-0ddf32bbc09add840	Node / Cluster
Asia Pacific (Tokyo)	ami-0bb9f8aebe7107773	Node / Cluster	ami-01f9486213e98936e	Node / Cluster
Israel (Tel Aviv)	ami-057d3a386f1d570d2	Node / Cluster	ami-09190f8670eb79b38	Node / Cluster
Canada (Central)	ami-008f4f7443ed48417	Node / Cluster	ami-096fcced7cd51a8b5	Node / Cluster
South America (Sao Paulo)	ami-06eb9680be441896f	Node / Cluster	ami-0aea33d4d697134a4	Node / Cluster
Asia Pacific (Hong Kong)	ami-013ee4e4efefa4b1d	Node / Cluster	ami-05839421e036e9430	Node / Cluster
Asia Pacific (Singapore)	ami-046c530128e955103	Node / Cluster	ami-0add7f11def75ff47	Node / Cluster
Asia Pacific (Sydney)	ami-0966c628bfabb7b17	Node / Cluster	ami-0c5d3e96d4e684ae7	Node / Cluster
Europe (Frankfurt)	ami-02a7cd6585258b687	Node / Cluster	ami-038e722143573a708	Node / Cluster
US East (N. Virginia)	ami-0fb5188e27a901e8f	Node / Cluster	ami-0db79b7737804f1da	Node / Cluster
US East (Ohio)	ami-0380b354c836bf59d	Node / Cluster	ami-04bf5200700d5bdc3	Node / Cluster
US West (N. California)	ami-0b6242e237fc43d09	Node / Cluster	ami-0cc18ffedb6281c53	Node / Cluster
US West (Oregon)	ami-00854f24e9f027e95	Node / Cluster	ami-07af72536bbb12de1	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?