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

Caution

You're viewing documentation for a deprecated 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.3.8¶

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-0237882e491bf7174	Node / Cluster	ami-010a4833ca71743b6	Node / Cluster
Africa (Cape Town)	ami-0260ff4111e2f9c66	Node / Cluster	ami-0055f52182c6806f3	Node / Cluster
Asia Pacific (Mumbai)	ami-0817335298c2d854e	Node / Cluster	ami-0fc3c4ac69b3594eb	Node / Cluster
Europe (Stockholm)	ami-03e3a5241441afc73	Node / Cluster	ami-01ddf42df3cd2f12c	Node / Cluster
Europe (Paris)	ami-0f8b238b2b44436ea	Node / Cluster	ami-0d835ff0b3f3251ba	Node / Cluster
Europe (Milan)	ami-0fa2dc48dae8b0a37	Node / Cluster	ami-0e35205adb29f8fe0	Node / Cluster
Europe (London)	ami-07a27523e21d918b2	Node / Cluster	ami-0b2c0ce012b5dca3d	Node / Cluster
Europe (Ireland)	ami-0c76b6a114d95c5f6	Node / Cluster	ami-0f7f50bd512b90b18	Node / Cluster
Asia Pacific (Osaka)	ami-0def2df2e64a38641	Node / Cluster	ami-06d3c7ede5f32d51c	Node / Cluster
Asia Pacific (Seoul)	ami-02a1f33a8dfa7dcc1	Node / Cluster	ami-0b85d3ac940a7dae1	Node / Cluster
Middle East (Bahrain)	ami-0dda99f4d2a20b1ca	Node / Cluster	ami-013fae8e2d8262232	Node / Cluster
Asia Pacific (Tokyo)	ami-03084e4015c97df29	Node / Cluster	ami-0de8e954acf3f2a0a	Node / Cluster
Israel (Tel Aviv)	ami-03085d536a4b341fc	Node / Cluster	ami-0a25a6de143bfc2aa	Node / Cluster
Canada (Central)	ami-0c438cad37b0ce6af	Node / Cluster	ami-04482bffc2cfd3a4d	Node / Cluster
South America (Sao Paulo)	ami-07860c1b99f0b6cff	Node / Cluster	ami-00dadfd99b2f56a0c	Node / Cluster
Asia Pacific (Hong Kong)	ami-03f4d2fb6408beaaf	Node / Cluster	ami-0021fe0ce761c52ed	Node / Cluster
Asia Pacific (Singapore)	ami-0c0452f2fd0e06914	Node / Cluster	ami-053527f6ae56a0a43	Node / Cluster
Asia Pacific (Sydney)	ami-0010e6fb1e0ddec24	Node / Cluster	ami-09fccdb6ac90d7854	Node / Cluster
Europe (Frankfurt)	ami-0af001bd204e281c1	Node / Cluster	ami-0353c1c151c60c123	Node / Cluster
US East (N. Virginia)	ami-0cf8ce011a4ced812	Node / Cluster	ami-04fbe176b02cbd3c1	Node / Cluster
US East (Ohio)	ami-0f0bf6071dc9eccec	Node / Cluster	ami-009d677e7b5028841	Node / Cluster
US West (N. California)	ami-030aa5e87a90cbf84	Node / Cluster	ami-07be78969746879c3	Node / Cluster
US West (Oregon)	ami-0539b1bfd903ebb8c	Node / Cluster	ami-01094afbf4fb56869	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?