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.

6.1.5¶

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-0bf5519c3a7a61286	Node / Cluster	ami-060151ddb88470d55	Node / Cluster
Africa (Cape Town)	ami-0107d5e537fcaee2a	Node / Cluster	ami-09e9c2f8697594d6e	Node / Cluster
Asia Pacific (Mumbai)	ami-032a25b79cd178e91	Node / Cluster	ami-036b0a245686ea6f1	Node / Cluster
Europe (Stockholm)	ami-00a77c85ca97232e6	Node / Cluster	ami-032d376bc36982f40	Node / Cluster
Europe (Paris)	ami-0502d96d375662959	Node / Cluster	ami-01899b40ec3e131ea	Node / Cluster
Europe (Milan)	ami-048cfc25e591506c4	Node / Cluster	ami-05bcbc4959b925efc	Node / Cluster
Europe (London)	ami-00ec8ee7fa48f3f01	Node / Cluster	ami-09bb9833b8caf944a	Node / Cluster
Europe (Ireland)	ami-0f71cb47c2b71a2d0	Node / Cluster	ami-0da867f88c71b4672	Node / Cluster
Asia Pacific (Osaka)	ami-0a74323c78b0129b9	Node / Cluster	ami-015a181cb6dec2d53	Node / Cluster
Asia Pacific (Seoul)	ami-0433e83edb41fc351	Node / Cluster	ami-048781979c62508d7	Node / Cluster
Middle East (Bahrain)	ami-0c21b23309dd5aaba	Node / Cluster	ami-00f41c26133a4b2c2	Node / Cluster
Asia Pacific (Tokyo)	ami-0cee8b2a408b8c16d	Node / Cluster	ami-0ea5ef302305e381b	Node / Cluster
Israel (Tel Aviv)	ami-02ae44cc5b12516d9	Node / Cluster	ami-0344bb742967c2766	Node / Cluster
Canada (Central)	ami-02aeb4c37081ecd5e	Node / Cluster	ami-0a665bfe5148fb13d	Node / Cluster
South America (Sao Paulo)	ami-00a88515a17b16fec	Node / Cluster	ami-07762ca70d1b37fa8	Node / Cluster
Asia Pacific (Hong Kong)	ami-0b1a8a7960a453acb	Node / Cluster	ami-09fb4d40c31314dd4	Node / Cluster
Asia Pacific (Singapore)	ami-0f4fc7ff02fbea612	Node / Cluster	ami-0f62484fafc9efe34	Node / Cluster
Asia Pacific (Sydney)	ami-03c72a87dc597f425	Node / Cluster	ami-03a45f219c1e22301	Node / Cluster
Europe (Frankfurt)	ami-01c54cbee34fbf6e0	Node / Cluster	ami-07d8c69048206e0f4	Node / Cluster
Asia Pacific (Jakarta)	ami-093b9d5d60532fdee	Node / Cluster	ami-06149b6f914c20e56	Node / Cluster
US East (N. Virginia)	ami-08591f5021c8990a3	Node / Cluster	ami-024d06f635f6d8201	Node / Cluster
US East (Ohio)	ami-0d4c9405c62e4d157	Node / Cluster	ami-0e70a5431bcf1d702	Node / Cluster
US West (N. California)	ami-0e57b05825eb75d6f	Node / Cluster	ami-06b2c7a8980e2cc93	Node / Cluster
US West (Oregon)	ami-04a2b5af764d73277	Node / Cluster	ami-05b6637ef701176c1	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?