ScyllaDB Docs ScyllaDB Enterprise Getting Started Install ScyllaDB Enterprise Launch ScyllaDB on AWS

Launch ScyllaDB on AWS¶

This article will guide you through self-managed ScyllaDB Enterprise 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.

2024.2.4¶

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-0ce2b1f195838a923	Node / Cluster	ami-041560d82f6793d81	Node / Cluster
Africa (Cape Town)	ami-027f82382182ae0d5	Node / Cluster	ami-06e777bd537622b3b	Node / Cluster
Asia Pacific (Mumbai)	ami-0e72c0f87df3a5aa1	Node / Cluster	ami-0d3507002f3533f21	Node / Cluster
Europe (Stockholm)	ami-0e5de97a66bf27de2	Node / Cluster	ami-0f25d69461908056c	Node / Cluster
Europe (Paris)	ami-093d986bf12331325	Node / Cluster	ami-0bbd9f6f6d4ad2759	Node / Cluster
Europe (Milan)	ami-0f222dd4f96364a9e	Node / Cluster	ami-0cfe2604d8efff4ea	Node / Cluster
Europe (London)	ami-08d50051f76751c01	Node / Cluster	ami-0ef6eb80894161c4d	Node / Cluster
Europe (Ireland)	ami-0164409bac8c99607	Node / Cluster	ami-082112e4cd5b79ebf	Node / Cluster
Asia Pacific (Osaka)	ami-04449425fc565f1c6	Node / Cluster	ami-0e5a42655198710df	Node / Cluster
Asia Pacific (Seoul)	ami-00392aa1bc509e162	Node / Cluster	ami-0e1e1ae55145d451c	Node / Cluster
Middle East (Bahrain)	ami-047d44d8dfb580e4e	Node / Cluster	ami-0d663dbfa857060fa	Node / Cluster
Asia Pacific (Tokyo)	ami-078bbe8989b0a7652	Node / Cluster	ami-0fa46ebbc4f24a5ef	Node / Cluster
Israel (Tel Aviv)	ami-0b82b381b61537d11	Node / Cluster	ami-0173d1ea92939aa0b	Node / Cluster
Canada (Central)	ami-09a89571927a6e647	Node / Cluster	ami-0bfc6f82c9f5ef80b	Node / Cluster
South America (Sao Paulo)	ami-000e49c5c6a137172	Node / Cluster	ami-098bb65704ad26db4	Node / Cluster
Asia Pacific (Hong Kong)	ami-03bb61708a68533fa	Node / Cluster	ami-012dc2a4f52d8bea8	Node / Cluster
Asia Pacific (Singapore)	ami-07ba3cdd9815e91d4	Node / Cluster	ami-0936eb40347f75a5e	Node / Cluster
Asia Pacific (Sydney)	ami-07dfd438808cd49ef	Node / Cluster	ami-023ea8cd7826c0078	Node / Cluster
Europe (Frankfurt)	ami-0994159ae3c0a535d	Node / Cluster	ami-0650cb7019dbb1007	Node / Cluster
Asia Pacific (Jakarta)	ami-045ad1e20cb5bbeb2	Node / Cluster	ami-03ffda538553a2adf	Node / Cluster
US East (N. Virginia)	ami-04c1efb7a7322d71e	Node / Cluster	ami-01121d395c4fdc0e3	Node / Cluster
US East (Ohio)	ami-0ea89ac06cb2aee1b	Node / Cluster	ami-0674c4d6838710052	Node / Cluster
US West (N. California)	ami-08e1886a6153db567	Node / Cluster	ami-0b600123fc60cd49b	Node / Cluster
US West (Oregon)	ami-085d61e1a58f7b5a8	Node / Cluster	ami-0206fb7df305459fb	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
Configure Security Group. Make sure all ScyllaDB ports are open.
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?