Caution

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

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

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-0eaf96df7f5df8df6	Node / Cluster	ami-0c6e5bd2d8bc7fa4c	Node / Cluster
Africa (Cape Town)	ami-0da3286e6782ec254	Node / Cluster	ami-0797ef54628d8250f	Node / Cluster
Asia Pacific (Mumbai)	ami-0eb87924dea196353	Node / Cluster	ami-08ba7edf6b9ab7c9f	Node / Cluster
Europe (Stockholm)	ami-04b1b379a82e2b3c4	Node / Cluster	ami-070cb78d3cf921e02	Node / Cluster
Europe (Paris)	ami-08ae15e57d83d5a3f	Node / Cluster	ami-07a7e6bad872430f7	Node / Cluster
Europe (Milan)	ami-0404be40dddd62b22	Node / Cluster	ami-0b92e3769914f3bc1	Node / Cluster
Europe (London)	ami-033062beb647b7103	Node / Cluster	ami-0ab602e930da7403d	Node / Cluster
Europe (Ireland)	ami-00afd9705cd2bb7e0	Node / Cluster	ami-083b3204633b55465	Node / Cluster
Asia Pacific (Osaka)	ami-0229862f5256b84c8	Node / Cluster	ami-093baf133f999079e	Node / Cluster
Asia Pacific (Seoul)	ami-06ec678db9d1f5902	Node / Cluster	ami-0f3807be973b8cd68	Node / Cluster
Middle East (Bahrain)	ami-0c94568e8345fdb61	Node / Cluster	ami-021757d9bfcab1310	Node / Cluster
Asia Pacific (Tokyo)	ami-08353051243d0fd13	Node / Cluster	ami-033bbb7600d18f83e	Node / Cluster
Israel (Tel Aviv)	ami-099bf5a19646ee26e	Node / Cluster	ami-0f6fee68789f7a186	Node / Cluster
Canada (Central)	ami-09e0772db0e54d9c8	Node / Cluster	ami-033cd7549cb03a62b	Node / Cluster
South America (Sao Paulo)	ami-0c809696d794bd813	Node / Cluster	ami-00fd84c5108889b45	Node / Cluster
Asia Pacific (Hong Kong)	ami-06c0a8f3f83c7c947	Node / Cluster	ami-06496c4801abb60c1	Node / Cluster
Asia Pacific (Singapore)	ami-0bbd4924ee4d6586e	Node / Cluster	ami-0178a4b699a031c8a	Node / Cluster
Asia Pacific (Sydney)	ami-0210f7e8bc6605cf9	Node / Cluster	ami-09c2cbf1da1d9bc87	Node / Cluster
Europe (Frankfurt)	ami-08053926c6ca4137d	Node / Cluster	ami-05be71994ad447e9e	Node / Cluster
Asia Pacific (Jakarta)	ami-09bfe455e62d13f7d	Node / Cluster	ami-04d534513b8801730	Node / Cluster
US East (N. Virginia)	ami-0222c7fa4f844fa69	Node / Cluster	ami-0188398d33b9efc57	Node / Cluster
US East (Ohio)	ami-019270817dcb0eb51	Node / Cluster	ami-072ba15ae2747392e	Node / Cluster
US West (N. California)	ami-04c94207a49a4af08	Node / Cluster	ami-02ccec8c5a36d3d37	Node / Cluster
US West (Oregon)	ami-0c0b9bb74857f9572	Node / Cluster	ami-03d54aa66fdbac6c8	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?