ScyllaDB Docs ScyllaDB Open Source Getting Started Install ScyllaDB Launch ScyllaDB on AWS

Caution

You're viewing documentation for a previous version of ScyllaDB Open Source. 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.

5.4.9¶

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-025878b48a34010f8	Node / Cluster	ami-09f3e188966bf48a9	Node / Cluster
Africa (Cape Town)	ami-0eec7e29f4cdcb49a	Node / Cluster	ami-06cad87861f6019d0	Node / Cluster
Asia Pacific (Mumbai)	ami-001652dda5b3c1c60	Node / Cluster	ami-0d36bb8264f06a24b	Node / Cluster
Europe (Stockholm)	ami-02ea1d8f254f6b740	Node / Cluster	ami-087fd32d7ee34ba30	Node / Cluster
Europe (Paris)	ami-0cff670fa41b43381	Node / Cluster	ami-0b1ffde7a20bddbb3	Node / Cluster
Europe (Milan)	ami-02c5b7c9aa419ae2e	Node / Cluster	ami-06d32ae0c0c25a8c6	Node / Cluster
Europe (London)	ami-03a6c8ed2bbb7ec8f	Node / Cluster	ami-00911f8edbdc1b27a	Node / Cluster
Europe (Ireland)	ami-0beab9bbe8eb2029e	Node / Cluster	ami-0d563b1616e608be0	Node / Cluster
Asia Pacific (Osaka)	ami-001f6e91513656544	Node / Cluster	ami-058a4b893754512fe	Node / Cluster
Asia Pacific (Seoul)	ami-0d4098fcdc0bb62d3	Node / Cluster	ami-0440f47738fbdd2be	Node / Cluster
Middle East (Bahrain)	ami-0078587dedf0c1596	Node / Cluster	ami-0cca6c506f8b5f9fd	Node / Cluster
Asia Pacific (Tokyo)	ami-0ea18016eb46165fb	Node / Cluster	ami-06ef9b7d1c72aa12e	Node / Cluster
Israel (Tel Aviv)	ami-0b4ea91bed351b261	Node / Cluster	ami-0d670b3356877aff9	Node / Cluster
Canada (Central)	ami-07e7d65e5ff5d6bad	Node / Cluster	ami-01231e049bcd6cec6	Node / Cluster
South America (Sao Paulo)	ami-04bc8176017fef213	Node / Cluster	ami-0a0752a757003b2c9	Node / Cluster
Asia Pacific (Hong Kong)	ami-0e0f8d86ccbdfae54	Node / Cluster	ami-0e8120de63bcc6c24	Node / Cluster
Asia Pacific (Singapore)	ami-08ffb1ccb8aaac7e4	Node / Cluster	ami-06186733a315d7312	Node / Cluster
Asia Pacific (Sydney)	ami-0b4e6d06569f71113	Node / Cluster	ami-03f7bc289be516219	Node / Cluster
Europe (Frankfurt)	ami-00eca7e484aba7b55	Node / Cluster	ami-04d8ef2a7a4261c7e	Node / Cluster
Asia Pacific (Jakarta)	ami-02a9d85a62a9156a7	Node / Cluster	ami-0263d2fe4adef34a4	Node / Cluster
US East (N. Virginia)	ami-002af14aef3a779c0	Node / Cluster	ami-0a01ff3c9c0bc4f9f	Node / Cluster
US East (Ohio)	ami-07b79b239adaf3daf	Node / Cluster	ami-00aacbc488a4ed1b5	Node / Cluster
US West (N. California)	ami-0114cdda366104a26	Node / Cluster	ami-026d80124beeb9322	Node / Cluster
US West (Oregon)	ami-06629e5df2a9a2178	Node / Cluster	ami-03fffcffb0628a1af	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 and the JMX component are 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?