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

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-0df42ab0b340c440a	Node / Cluster	ami-09f22f1628ac0e2fe	Node / Cluster
Africa (Cape Town)	ami-0e250d55e0a820cd1	Node / Cluster	ami-0b4ab251b8107ce88	Node / Cluster
Asia Pacific (Mumbai)	ami-0546b7656e3361178	Node / Cluster	ami-03521bf2b985bf2bf	Node / Cluster
Europe (Stockholm)	ami-0685bdde24cc32009	Node / Cluster	ami-05b51aec7e5fde9c4	Node / Cluster
Europe (Paris)	ami-007e04e8decd8abad	Node / Cluster	ami-09b0fb82587fe78db	Node / Cluster
Europe (Milan)	ami-0d29db427bb7922db	Node / Cluster	ami-0e18dce72a0dec39f	Node / Cluster
Europe (London)	ami-000b56ad1ede50832	Node / Cluster	ami-0381aa777c434cfbd	Node / Cluster
Europe (Ireland)	ami-0ebbb0254cdba0e56	Node / Cluster	ami-03713d4248e9d4c2b	Node / Cluster
Asia Pacific (Osaka)	ami-0ccaeb33e2ed2d18e	Node / Cluster	ami-0d486a329a067b445	Node / Cluster
Asia Pacific (Seoul)	ami-07d43925e37953a0b	Node / Cluster	ami-00c8aabc8c8626956	Node / Cluster
Middle East (Bahrain)	ami-082b81d9f9089b4fc	Node / Cluster	ami-00cad9afb7c5c6f87	Node / Cluster
Asia Pacific (Tokyo)	ami-0d344989fe5ffcbc1	Node / Cluster	ami-0840f618e76df4c22	Node / Cluster
Israel (Tel Aviv)	ami-04e6637129fd0738a	Node / Cluster	ami-09c926ba5e8a2a36c	Node / Cluster
Canada (Central)	ami-0206de17aaf8a3266	Node / Cluster	ami-0d0542021e15dc512	Node / Cluster
South America (Sao Paulo)	ami-00d1c475ea63459f6	Node / Cluster	ami-0e473781c9260aaa7	Node / Cluster
Asia Pacific (Hong Kong)	ami-0dab06eb69db9681c	Node / Cluster	ami-074aa5af890341ca4	Node / Cluster
Asia Pacific (Singapore)	ami-0585d00fa65d2dd46	Node / Cluster	ami-02470c0ff304bd583	Node / Cluster
Asia Pacific (Sydney)	ami-04e5041c349a6dca3	Node / Cluster	ami-01acf9b685703e2a0	Node / Cluster
Europe (Frankfurt)	ami-03bf78bec6079d9a6	Node / Cluster	ami-085b1336e4a4921e0	Node / Cluster
US East (N. Virginia)	ami-06214cf7733ad41cb	Node / Cluster	ami-02a799ca9a8b4c50a	Node / Cluster
US East (Ohio)	ami-05f5fc56c2b872896	Node / Cluster	ami-0cd0ee3e89b3cd040	Node / Cluster
US West (N. California)	ami-002e4e363c9e5096f	Node / Cluster	ami-06bde5525b8517d66	Node / Cluster
US West (Oregon)	ami-01770a93876cd473f	Node / Cluster	ami-08c09fd78f0eabdae	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?