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

Launch ScyllaDB 2026.1 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.

2026.1.3¶

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-0d58908b96929a1eb	Node / Cluster	ami-0a4827e3dd9d1f2b9	Node / Cluster
Africa (Cape Town)	ami-0f87040de2dc27ff6	Node / Cluster	ami-08e74af09669edfab	Node / Cluster
Asia Pacific (Mumbai)	ami-0f31616a47a91b659	Node / Cluster	ami-0a2d748ff1b873a62	Node / Cluster
Europe (Stockholm)	ami-0f71fc6f3a1a732b6	Node / Cluster	ami-0deb01535f39dec79	Node / Cluster
Europe (Paris)	ami-07f02f3c7777d8972	Node / Cluster	ami-012a4e9851e15fa2b	Node / Cluster
Europe (Milan)	ami-0be22dd30eae79569	Node / Cluster	ami-0e243f0779e7a0336	Node / Cluster
Europe (London)	ami-011641e9449569133	Node / Cluster	ami-08be31ba66aa5a373	Node / Cluster
Europe (Ireland)	ami-071f256e35c90a94c	Node / Cluster	ami-061097c7a1aa97f58	Node / Cluster
Asia Pacific (Osaka)	ami-0d185cf08943e561f	Node / Cluster	ami-09c9c90399f6b2b43	Node / Cluster
Asia Pacific (Seoul)	ami-0584a457e75ba09c0	Node / Cluster	ami-04747145752c85f87	Node / Cluster
Asia Pacific (Tokyo)	ami-040b674c1940104c0	Node / Cluster	ami-0e88b2e1bafffe024	Node / Cluster
Israel (Tel Aviv)	ami-028ab8d04f269f399	Node / Cluster	ami-0437eabe00ce65dab	Node / Cluster
Canada (Central)	ami-0f9e690ecb54c806d	Node / Cluster	ami-02c82c9f8a66ebe57	Node / Cluster
South America (Sao Paulo)	ami-062eed2a299932d05	Node / Cluster	ami-0f4c7e730ae4f52a3	Node / Cluster
Asia Pacific (Hong Kong)	ami-0a8368c9f0ec01f20	Node / Cluster	ami-0341b9755324a80b2	Node / Cluster
Asia Pacific (Singapore)	ami-024e01809769e14d8	Node / Cluster	ami-017adcea60bf19b68	Node / Cluster
Asia Pacific (Sydney)	ami-02b926d3b8a6163db	Node / Cluster	ami-039dd263e544caa65	Node / Cluster
Europe (Frankfurt)	ami-04ca7332cc80fcbe1	Node / Cluster	ami-07dd7388e7439c7e5	Node / Cluster
US East (N. Virginia)	ami-04ac43ad4ba9fffe0	Node / Cluster	ami-0d7ac5b96c779de2d	Node / Cluster
US East (Ohio)	ami-05f788596039de054	Node / Cluster	ami-020e5164d763e61e9	Node / Cluster
US West (N. California)	ami-0c7f22c0ed7f53378	Node / Cluster	ami-02001f8626cbac08d	Node / Cluster
US West (Oregon)	ami-0b0727f9a9f70fb6e	Node / Cluster	ami-043e33086afef5a22	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?