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

Caution

You're viewing documentation for a previous version. Switch to the latest stable version.

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

View image details

Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
Asia Pacific (Hyderabad)	ami-0c720fd71efce420d	Node / Cluster	ami-0b56771b7d02ccd9f	Node / Cluster
Africa (Cape Town)	ami-015ae6f57e574059e	Node / Cluster	ami-093adaa6467d19f7e	Node / Cluster
Asia Pacific (Mumbai)	ami-04cd8ccaca157a797	Node / Cluster	ami-0f1b1894dde385d39	Node / Cluster
Europe (Stockholm)	ami-0ea2ec4076b98153a	Node / Cluster	ami-0abc61b24c9fab8d2	Node / Cluster
Europe (Paris)	ami-08175cbbcc95347cf	Node / Cluster	ami-075740fb8f44258c7	Node / Cluster
Europe (Milan)	ami-0f5f8a61e7d2e7bb4	Node / Cluster	ami-020f890668bf79ead	Node / Cluster
Europe (London)	ami-0150bace4f8480593	Node / Cluster	ami-07ee2e411a4eeba9d	Node / Cluster
Europe (Ireland)	ami-0e09e10f495f77ea5	Node / Cluster	ami-0124419d8400536da	Node / Cluster
Asia Pacific (Osaka)	ami-03865b37343dd0058	Node / Cluster	ami-094d650e94eebdcc9	Node / Cluster
Asia Pacific (Seoul)	ami-0a8699936ffdaa365	Node / Cluster	ami-04f78bb12a6b7e1d0	Node / Cluster
Middle East (Bahrain)	ami-031f09259464478de	Node / Cluster	ami-0c2cb64c6ad055a36	Node / Cluster
Asia Pacific (Tokyo)	ami-05f0a164a3f82e9f2	Node / Cluster	ami-05af9580d9a22d61b	Node / Cluster
Israel (Tel Aviv)	ami-02fe8ad3bca35c9e8	Node / Cluster	ami-0cbc0864e71833fc5	Node / Cluster
Canada (Central)	ami-080b5481470c2b59f	Node / Cluster	ami-01beba5ee8db8700b	Node / Cluster
South America (Sao Paulo)	ami-0d00eabf3cb338e94	Node / Cluster	ami-0a032bfaae2d39afb	Node / Cluster
Asia Pacific (Hong Kong)	ami-03cff6c799f6e3543	Node / Cluster	ami-03fa98f5961617528	Node / Cluster
Asia Pacific (Singapore)	ami-05f07e5ecc0c856b4	Node / Cluster	ami-071a563bb2a05b701	Node / Cluster
Asia Pacific (Sydney)	ami-0d5214b35c49c3a26	Node / Cluster	ami-02f53eeef9c358e21	Node / Cluster
Europe (Frankfurt)	ami-086b153611efeba84	Node / Cluster	ami-0f734fca26100d384	Node / Cluster
US East (N. Virginia)	ami-030774ae9abeca71c	Node / Cluster	ami-0f337ae6ad9538d62	Node / Cluster
US East (Ohio)	ami-038701d24f33b90e5	Node / Cluster	ami-0d36d7c742bcbeba3	Node / Cluster
US West (N. California)	ami-01ae044ede1fcc90e	Node / Cluster	ami-05f6ea305170e9d8c	Node / Cluster
US West (Oregon)	ami-0d15448ea04c00856	Node / Cluster	ami-00b1d91f387534e4a	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?