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

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-02d485a0c06f6029f	Node / Cluster	ami-027f671320721dcf2	Node / Cluster
Africa (Cape Town)	ami-04a2c0dee50173953	Node / Cluster	ami-00678f8641d2063d8	Node / Cluster
Asia Pacific (Mumbai)	ami-04fe6dcb6e38620de	Node / Cluster	ami-0ce9362d562ee1d29	Node / Cluster
Europe (Stockholm)	ami-07e0bdc0d67026e43	Node / Cluster	ami-0a6a470b7cb83fdb7	Node / Cluster
Europe (Paris)	ami-051e641c73415a1e2	Node / Cluster	ami-03d5ae69e79503aba	Node / Cluster
Europe (Milan)	ami-0ba6f7bdfef28feb4	Node / Cluster	ami-02061edba41fa03a1	Node / Cluster
Europe (London)	ami-07d7cd85a477c8b7b	Node / Cluster	ami-07accdbb35c1c15a7	Node / Cluster
Europe (Ireland)	ami-0dfa67be7d3390229	Node / Cluster	ami-03c4048aa21b558ae	Node / Cluster
Asia Pacific (Osaka)	ami-02d7b7ba7ca0b0f6d	Node / Cluster	ami-07d49106d666a741a	Node / Cluster
Asia Pacific (Seoul)	ami-04df6bb06a03f2a1e	Node / Cluster	ami-0f68d81682c8ecce4	Node / Cluster
Middle East (Bahrain)	ami-07df861fd1990e217	Node / Cluster	ami-0ee7e995afdf6d43a	Node / Cluster
Asia Pacific (Tokyo)	ami-0548fd53c6dc27fda	Node / Cluster	ami-05f49dfc216dbe474	Node / Cluster
Israel (Tel Aviv)	ami-02203d73af90599dd	Node / Cluster	ami-0193bedf343c7de8b	Node / Cluster
Canada (Central)	ami-02841989541443217	Node / Cluster	ami-0a5980a831201900c	Node / Cluster
South America (Sao Paulo)	ami-07e390619bfdd130e	Node / Cluster	ami-090d955bd10d56770	Node / Cluster
Asia Pacific (Hong Kong)	ami-029633fb55869d421	Node / Cluster	ami-0ca12d9380131f419	Node / Cluster
Asia Pacific (Singapore)	ami-07a122f69c0de4496	Node / Cluster	ami-08f451850fb0980fc	Node / Cluster
Asia Pacific (Sydney)	ami-0dc85d3c21fa6dd45	Node / Cluster	ami-0f71e96b6ffc21498	Node / Cluster
Europe (Frankfurt)	ami-0f0d490bf0f15f045	Node / Cluster	ami-00823a019cc37eb8d	Node / Cluster
US East (N. Virginia)	ami-0ec7b8e641af346e0	Node / Cluster	ami-06887bd7fd1520615	Node / Cluster
US East (Ohio)	ami-01439f58dd76568d8	Node / Cluster	ami-0c3b39d3767ea4204	Node / Cluster
US West (N. California)	ami-0a2fe9a2704842d39	Node / Cluster	ami-0c1984dfc35a79c75	Node / Cluster
US West (Oregon)	ami-0aa318060ae238e7f	Node / Cluster	ami-0d03e6ae86ca3bc4b	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?