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

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-005254499f379dbf0	Node / Cluster	ami-062fac34ea8759c53	Node / Cluster
Africa (Cape Town)	ami-0002f422fca8592b4	Node / Cluster	ami-0dc719daff7843de4	Node / Cluster
Asia Pacific (Mumbai)	ami-0b972d57ce04bd339	Node / Cluster	ami-0e4e6d05956abf0ce	Node / Cluster
Europe (Stockholm)	ami-05bea3590facac37f	Node / Cluster	ami-0a837e5c79247c822	Node / Cluster
Europe (Paris)	ami-0967af4af800fe38e	Node / Cluster	ami-03f439363ba81ede4	Node / Cluster
Europe (Milan)	ami-0e0028ea83c94cf8d	Node / Cluster	ami-0f1970d2b655de440	Node / Cluster
Europe (London)	ami-0dc0bf82c2109a696	Node / Cluster	ami-064f2995331bb9bc5	Node / Cluster
Europe (Ireland)	ami-0e2a4118713ef4124	Node / Cluster	ami-053e279fcdc00e7f7	Node / Cluster
Asia Pacific (Osaka)	ami-0c9d4f180aff1113d	Node / Cluster	ami-014a5fc3cfe051b80	Node / Cluster
Asia Pacific (Seoul)	ami-00ddf1927a244ddf3	Node / Cluster	ami-083961bc4d1ab1fba	Node / Cluster
Middle East (Bahrain)	ami-0aa5f2a390753c704	Node / Cluster	ami-0e98e6f2163ecfd76	Node / Cluster
Asia Pacific (Tokyo)	ami-07d91c4f49021a6b0	Node / Cluster	ami-0c142e088a829f7df	Node / Cluster
Israel (Tel Aviv)	ami-087419950daf76f93	Node / Cluster	ami-03600eef5dd157ee0	Node / Cluster
Canada (Central)	ami-0bf343637349c386b	Node / Cluster	ami-006d18ee0f7f49ca6	Node / Cluster
South America (Sao Paulo)	ami-093a693c7170a07c8	Node / Cluster	ami-0179192ef0ed6374f	Node / Cluster
Asia Pacific (Hong Kong)	ami-0d737de5674421f17	Node / Cluster	ami-0e32491f64e1477da	Node / Cluster
Asia Pacific (Singapore)	ami-052791ad6bb3f5e31	Node / Cluster	ami-07de97364ff15fb0d	Node / Cluster
Asia Pacific (Sydney)	ami-049467ce4ffb184ba	Node / Cluster	ami-01bd23c1899e3e7b3	Node / Cluster
Europe (Frankfurt)	ami-0e63da3dcf297790a	Node / Cluster	ami-0fafe118da2d266b3	Node / Cluster
US East (N. Virginia)	ami-0bad8b290783c94c3	Node / Cluster	ami-05ab72f8632fd10df	Node / Cluster
US East (Ohio)	ami-06e8d1ca44d93fec1	Node / Cluster	ami-0b0df7c4fe5decd29	Node / Cluster
US West (N. California)	ami-0d3c84cf4297fe32c	Node / Cluster	ami-0e320d616a69d2b5f	Node / Cluster
US West (Oregon)	ami-056ed5a01327e0f2d	Node / Cluster	ami-0df865fd772799d9f	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?