ScyllaDB Docs ScyllaDB Open Source 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.

6.2.2¶

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-0e39f522da779a494	Node / Cluster	ami-065d9161792142687	Node / Cluster
Africa (Cape Town)	ami-09ccad7c6e591b807	Node / Cluster	ami-0275c35145d0abe3c	Node / Cluster
Asia Pacific (Mumbai)	ami-0319efa19fe93fa22	Node / Cluster	ami-0c18bee1e5e0e4fcd	Node / Cluster
Europe (Stockholm)	ami-0d579d7135bb47d3e	Node / Cluster	ami-06df2ac17c550ae1e	Node / Cluster
Europe (Paris)	ami-0083024b73fcf8b4c	Node / Cluster	ami-07b81fb80feba7963	Node / Cluster
Europe (Milan)	ami-04a7539aa627b76b5	Node / Cluster	ami-0ffecc753ba2bae5f	Node / Cluster
Europe (London)	ami-020450b9f12ebde57	Node / Cluster	ami-0b42d65880e5c69bc	Node / Cluster
Europe (Ireland)	ami-04541afe5ffea0038	Node / Cluster	ami-03dae9909de35247a	Node / Cluster
Asia Pacific (Osaka)	ami-00fe76cc251e6bf42	Node / Cluster	ami-02124faec329fefb4	Node / Cluster
Asia Pacific (Seoul)	ami-02f833f2c58e8fcef	Node / Cluster	ami-0e37bcd0856b26a1b	Node / Cluster
Middle East (Bahrain)	ami-03d8ee3c6162b0131	Node / Cluster	ami-0da79536e64f95919	Node / Cluster
Asia Pacific (Tokyo)	ami-0c16ada0621856b4f	Node / Cluster	ami-0ddc63011d20e5aad	Node / Cluster
Israel (Tel Aviv)	ami-016828b74820eddd3	Node / Cluster	ami-05fe25136fb87dfcc	Node / Cluster
Canada (Central)	ami-01fc0b04e9a46883a	Node / Cluster	ami-0c9e43ca8a205f613	Node / Cluster
South America (Sao Paulo)	ami-012e523926c478c79	Node / Cluster	ami-05b0275a237182203	Node / Cluster
Asia Pacific (Hong Kong)	ami-0e843e7989451309b	Node / Cluster	ami-0c426794b60a5658c	Node / Cluster
Asia Pacific (Singapore)	ami-05ecdf35102f83853	Node / Cluster	ami-07c0d8468c86e94a6	Node / Cluster
Asia Pacific (Sydney)	ami-0cae1c25e1d1d0ae1	Node / Cluster	ami-004f8baacfd413dbf	Node / Cluster
Europe (Frankfurt)	ami-04d893f7db37773b4	Node / Cluster	ami-0742ee9715bc8f5fa	Node / Cluster
Asia Pacific (Jakarta)	ami-0a9b9fc8d86c4f83c	Node / Cluster	ami-0341fa1f21de83fa3	Node / Cluster
US East (N. Virginia)	ami-01431b9bf2e7cc148	Node / Cluster	ami-0825a518ab80e05bf	Node / Cluster
US East (Ohio)	ami-02393764f1aa1b85b	Node / Cluster	ami-0cd9a909ca4a47f9d	Node / Cluster
US West (N. California)	ami-07c1994abdc982adb	Node / Cluster	ami-0cc8e1f3259410889	Node / Cluster
US West (Oregon)	ami-0d31a68f80d06c304	Node / Cluster	ami-0ebc7169ec1c3436d	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?