Was this page helpful?
Caution
You're viewing documentation for a previous version of ScyllaDB Manual. 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.
2025.1.14¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-00ea0ed57b16dee78
ami-0c14b8c2526a84f07
Africa (Cape Town)
ami-09cda3ccfbe3836f9
ami-0da42dfc90fadc903
Asia Pacific (Mumbai)
ami-0c2db878a7808d933
ami-0167499da314f4bf8
Europe (Stockholm)
ami-09d521e94ed70ccfd
ami-03dabcae64436591c
Europe (Paris)
ami-0e6466bbea7f01ae7
ami-061bbbe28ec941567
Europe (Milan)
ami-00135d7147c5c44d8
ami-05ee3288e6b3d9772
Europe (London)
ami-05b3f8f01ef445659
ami-07525f7579c3820df
Europe (Ireland)
ami-0459171f60974618d
ami-0e73bb21491d0323e
Asia Pacific (Osaka)
ami-0066ccb60ded3e4d2
ami-0a9bcd56cff6d954c
Asia Pacific (Seoul)
ami-0eaa054807414195d
ami-0884f18360de2c2f5
Asia Pacific (Tokyo)
ami-03a74a5c9039c0ab4
ami-080a4c5984ccc0a8d
Israel (Tel Aviv)
ami-0d7b372456ab97e81
ami-073221e23dd8295cd
Canada (Central)
ami-0702f5b5776fa47c1
ami-00dc254de8911e2dc
South America (Sao Paulo)
ami-000c4f339ab7bea97
ami-05216539b53addf7c
Asia Pacific (Hong Kong)
ami-048d12228413e8d76
ami-035615f2e076bd91c
Asia Pacific (Singapore)
ami-023fe1b3ff45e5ea3
ami-09e29e0bbcf0f1d90
Asia Pacific (Sydney)
ami-03885b167bbaaafd6
ami-08b46c375bf250425
Europe (Frankfurt)
ami-05f7eb2664bd64f8e
ami-0f5c2b2c6371e82b4
US East (N. Virginia)
ami-0e531d1942d3e620b
ami-00c6b9d33aace3cad
US East (Ohio)
ami-0613f3faa001f0303
ami-06b844231ce3bae22
US West (N. California)
ami-0c32b10433aad9c16
ami-06892e3eb88133fe4
US West (Oregon)
ami-0d758c9223a5d916c
ami-0b5b0901d5763f8ba
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
seedsparameter - 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-ipThe default file paths:
The
scylla.yamlfile:/etc/scylla/scylla.yamlData:
/var/lib/scylla/
To check that the ScyllaDB server is running, run:
nodetool status
Next Steps¶
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