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

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-076fc5ba32c2c29da	Node / Cluster	ami-0373a1a7d2f015fae	Node / Cluster
Africa (Cape Town)	ami-03c35f796885ed4a9	Node / Cluster	ami-0a38b9e04f2a9dd5e	Node / Cluster
Asia Pacific (Mumbai)	ami-018650fbc61de9bbc	Node / Cluster	ami-0f4f6239d63779701	Node / Cluster
Europe (Stockholm)	ami-0127188a10afb5d33	Node / Cluster	ami-0e6109f7a6660710d	Node / Cluster
Europe (Paris)	ami-0cd9af394e724f836	Node / Cluster	ami-0bd796fb8f255b23f	Node / Cluster
Europe (Milan)	ami-0bc9397510f9a39f7	Node / Cluster	ami-0a695ec7cd072e2e5	Node / Cluster
Europe (London)	ami-04ec137f4c8e3cb2d	Node / Cluster	ami-01eb06d0b3cd74493	Node / Cluster
Europe (Ireland)	ami-055dc9ce1dc5ee9bd	Node / Cluster	ami-0ac9f799d0f225bd4	Node / Cluster
Asia Pacific (Osaka)	ami-0d734488b26fa7da4	Node / Cluster	ami-0d9995ef1d71d41ba	Node / Cluster
Asia Pacific (Seoul)	ami-0dfeffb67ede134f6	Node / Cluster	ami-0067ad02504c3f1fd	Node / Cluster
Middle East (Bahrain)	ami-07a18610f5c9fca16	Node / Cluster	ami-059e5cb633e9cd668	Node / Cluster
Asia Pacific (Tokyo)	ami-0711bdf9b5b33b736	Node / Cluster	ami-09bb1d1ab54ed3f38	Node / Cluster
Israel (Tel Aviv)	ami-012ee94b31bd4210f	Node / Cluster	ami-0eba44c260fbdbf32	Node / Cluster
Canada (Central)	ami-042ae6f53189fd645	Node / Cluster	ami-0e9b8e22d919dc1d6	Node / Cluster
South America (Sao Paulo)	ami-03996d2c87d6ea722	Node / Cluster	ami-0212f78d7016fd7a9	Node / Cluster
Asia Pacific (Hong Kong)	ami-09ad93af197b01f9b	Node / Cluster	ami-05f2beab104d444f6	Node / Cluster
Asia Pacific (Singapore)	ami-0c66fb33fe03e8948	Node / Cluster	ami-0ca5ff93cd49732a2	Node / Cluster
Asia Pacific (Sydney)	ami-0687e09532a878b9d	Node / Cluster	ami-049bf5daa83a06c55	Node / Cluster
Europe (Frankfurt)	ami-05fb351d7c8fc8666	Node / Cluster	ami-04148806c9ae315e9	Node / Cluster
Asia Pacific (Jakarta)	ami-09d5a6a6b3d26c2df	Node / Cluster	ami-09dae24d085f820ea	Node / Cluster
US East (N. Virginia)	ami-0deef1e6ec677aea8	Node / Cluster	ami-0b984bd1f7271010a	Node / Cluster
US East (Ohio)	ami-06de569f6440b8d23	Node / Cluster	ami-013813eaf10ed2b87	Node / Cluster
US West (N. California)	ami-03ada8069cde98ff2	Node / Cluster	ami-06252c12a8b74dde6	Node / Cluster
US West (Oregon)	ami-0c086598b80c5b693	Node / Cluster	ami-0d9e5259e4c30e086	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?