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

Caution

You're viewing documentation for a previous version of ScyllaDB Manual. Switch to the latest stable version.

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

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-04ae632dd7e97702d	Node / Cluster	ami-0170a06b083ef4a1b	Node / Cluster
Africa (Cape Town)	ami-0949d3385e361bb91	Node / Cluster	ami-0d38c86173bd58602	Node / Cluster
Asia Pacific (Mumbai)	ami-049c70612ed233341	Node / Cluster	ami-0ebbb03161eff2d9b	Node / Cluster
Europe (Stockholm)	ami-055c211211f79a90c	Node / Cluster	ami-0c19c06ce37de9358	Node / Cluster
Europe (Paris)	ami-0a2162ba34e1cfa36	Node / Cluster	ami-0af84df32c257c64f	Node / Cluster
Europe (Milan)	ami-09648b456e07b3ab8	Node / Cluster	ami-0fa05091cb83c30ca	Node / Cluster
Europe (London)	ami-0cd96d730e6a27914	Node / Cluster	ami-05048aa836fcd4500	Node / Cluster
Europe (Ireland)	ami-0b0585d47598048a0	Node / Cluster	ami-01f4f675935401258	Node / Cluster
Asia Pacific (Osaka)	ami-0dbf4acceaa0f780a	Node / Cluster	ami-069e6ba94a072e75a	Node / Cluster
Asia Pacific (Seoul)	ami-0f42ebf88e359856b	Node / Cluster	ami-06fe3c0e019bc6221	Node / Cluster
Asia Pacific (Tokyo)	ami-00635d529785161d7	Node / Cluster	ami-08a7ffa45944ea5e4	Node / Cluster
Israel (Tel Aviv)	ami-0fb80b9d68e30d7ca	Node / Cluster	ami-0bafdd75b0535cee7	Node / Cluster
Canada (Central)	ami-015adca045692825d	Node / Cluster	ami-010990f382e0f61f5	Node / Cluster
South America (Sao Paulo)	ami-02d1443de35e091a0	Node / Cluster	ami-0fcdaeeafbaf9e920	Node / Cluster
Asia Pacific (Hong Kong)	ami-0b3e7306be0a875c8	Node / Cluster	ami-04382fcfb28be5090	Node / Cluster
Asia Pacific (Singapore)	ami-02668385f525bcb2d	Node / Cluster	ami-0cacd1ae4bafe2316	Node / Cluster
Asia Pacific (Sydney)	ami-05f3bb1e12376d592	Node / Cluster	ami-0ca4cbb1270e52b84	Node / Cluster
Europe (Frankfurt)	ami-090b5d408a0f13a30	Node / Cluster	ami-0fe6389e71fe1834a	Node / Cluster
US East (N. Virginia)	ami-0bab321fdc66e22db	Node / Cluster	ami-014724020b9e7e055	Node / Cluster
US East (Ohio)	ami-051cf46029c51f314	Node / Cluster	ami-0cc57f51c496f61cb	Node / Cluster
US West (N. California)	ami-054fbae2b284e0086	Node / Cluster	ami-0625428632ed3a169	Node / Cluster
US West (Oregon)	ami-0df45c618bac47be5	Node / Cluster	ami-0959a18b2b6ff17a7	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?