Was this page helpful?
Caution
You're viewing documentation for a previous version of ScyllaDB Manual. Switch to the latest stable version.
Launch ScyllaDB 2026.2 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.
2026.2.7¶
Region
x86 AMI ID
Launch x86
ARM AMI ID
Launch ARM
Asia Pacific (Hyderabad)
ami-0ac824266bcfe2464
ami-06f09402e6560ab02
Africa (Cape Town)
ami-0b66b045f7b8a7166
ami-0d6881a8fe12161f5
Asia Pacific (Mumbai)
ami-0832259e7c4652374
ami-093610f526a784b3e
Europe (Stockholm)
ami-01b5313a6fd48c54a
ami-088af02fec80bcf04
Europe (Paris)
ami-0682339952687a1a0
ami-0cf5d380baaf3a9f7
Europe (Milan)
ami-0f1a141c384218d53
ami-0e5fdebbede7b437e
Europe (London)
ami-0d28ccd5d950602b2
ami-0cbbf98057cf7c803
Europe (Ireland)
ami-05edfb20bedc82a54
ami-04d8c0acf253ac73b
Asia Pacific (Osaka)
ami-05ccb9353392e2c91
ami-0625d27df3d416e68
Asia Pacific (Seoul)
ami-0c2d516df722acfa6
ami-0ff67c15d48267a95
Asia Pacific (Tokyo)
ami-005bbf8274ec94a84
ami-04144d30f177bdc9d
Israel (Tel Aviv)
ami-0290147922167b53b
ami-02376958c4744845e
Canada (Central)
ami-05ea475ccdf5a4977
ami-0206da369150b9f2e
South America (Sao Paulo)
ami-019d228ae3edd0516
ami-0353ef7856b67b374
Asia Pacific (Hong Kong)
ami-030c80dbf661d3482
ami-0e85005f250d20aea
Asia Pacific (Singapore)
ami-07c27999d4891c927
ami-09e45206b3bd303ff
Asia Pacific (Sydney)
ami-0e32601ca7b21aef9
ami-0ba8cc4e1e26654bd
Europe (Frankfurt)
ami-0a9892711f8976c47
ami-0d966db7bc7331679
US East (N. Virginia)
ami-0185061de76dc53b4
ami-050db0d2de3ef509f
US East (Ohio)
ami-0dace55e3cb53bc2c
ami-0928b4c6748f58c73
US West (N. California)
ami-049c3e526814ab41d
ami-0be32eb86c3ab6c40
US West (Oregon)
ami-0f3eef9e323075fc4
ami-0e3d15973f3f92d1f
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