ScyllaDB University LIVE, FREE Virtual Training Event | March 21
Register for Free
ScyllaDB Documentation Logo Documentation
  • Deployments
    • Cloud
    • Server
  • Tools
    • ScyllaDB Manager
    • ScyllaDB Monitoring Stack
    • ScyllaDB Operator
  • Drivers
    • CQL Drivers
    • DynamoDB Drivers
    • Supported Driver Versions
  • Resources
    • ScyllaDB University
    • Community Forum
    • Tutorials
Install
Search Ask AI
ScyllaDB Docs ScyllaDB Manual Getting Started Install ScyllaDB Launch ScyllaDB on AWS
For AI agents: a documentation index is available at https://docs.scylladb.com/manual/branch-2025.1/llms.txt. A Markdown version of this page is at https://docs.scylladb.com/manual/branch-2025.1/getting-started/install-scylla/launch-on-aws.md.

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¶

  1. 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.15¶

    Region

    x86 AMI ID

    Launch x86

    ARM AMI ID

    Launch ARM

    Asia Pacific (Hyderabad)

    ami-0be9bc9a21bebb378

    Node / Cluster

    ami-05873df0f754a8359

    Node / Cluster

    Africa (Cape Town)

    ami-07a91a71dbeb55070

    Node / Cluster

    ami-0a5d4e49104881329

    Node / Cluster

    Asia Pacific (Mumbai)

    ami-0f62a461cd93bc752

    Node / Cluster

    ami-078472e6ed235ce6e

    Node / Cluster

    Europe (Stockholm)

    ami-09325bd9d5e6d29cd

    Node / Cluster

    ami-08e6b47e4b6cca01c

    Node / Cluster

    Europe (Paris)

    ami-0a7da2db882dc7178

    Node / Cluster

    ami-08b0c80438f87f950

    Node / Cluster

    Europe (Milan)

    ami-0aa46d88f07b2706f

    Node / Cluster

    ami-0c88dcc1aad72d434

    Node / Cluster

    Europe (London)

    ami-091913376819da553

    Node / Cluster

    ami-0107d915306c33147

    Node / Cluster

    Europe (Ireland)

    ami-0af29e4a837ca1fe4

    Node / Cluster

    ami-02a29e70c0395924c

    Node / Cluster

    Asia Pacific (Osaka)

    ami-03d3cf4c14a6e8b6d

    Node / Cluster

    ami-0fd54af073d8664ba

    Node / Cluster

    Asia Pacific (Seoul)

    ami-0b5275e54dc7f6955

    Node / Cluster

    ami-078c8e33f73abed3a

    Node / Cluster

    Asia Pacific (Tokyo)

    ami-0422ed5eec32f439d

    Node / Cluster

    ami-06d5091195ed27772

    Node / Cluster

    Israel (Tel Aviv)

    ami-0ed2f8b716b8aec05

    Node / Cluster

    ami-0711833f6b3af80a3

    Node / Cluster

    Canada (Central)

    ami-0a353228808febabd

    Node / Cluster

    ami-00c0a6ef3a8547303

    Node / Cluster

    South America (Sao Paulo)

    ami-0b8b7dbb3494ec826

    Node / Cluster

    ami-034ff0d8a68b9841a

    Node / Cluster

    Asia Pacific (Hong Kong)

    ami-0fc6655c7bc25ff0c

    Node / Cluster

    ami-0f9cea1c7dd506764

    Node / Cluster

    Asia Pacific (Singapore)

    ami-0198ab3ff9f7e0a1e

    Node / Cluster

    ami-0fd3e47875306349b

    Node / Cluster

    Asia Pacific (Sydney)

    ami-051a1e2d2a9688b5b

    Node / Cluster

    ami-0b76cdb68ffa00bd0

    Node / Cluster

    Europe (Frankfurt)

    ami-03d29a116ea5645e3

    Node / Cluster

    ami-09238786d3f345681

    Node / Cluster

    US East (N. Virginia)

    ami-0c0d2a52abe3f494c

    Node / Cluster

    ami-0987ca9b63684cdfc

    Node / Cluster

    US East (Ohio)

    ami-0e856f9a67face25d

    Node / Cluster

    ami-096a1cb5b259bed41

    Node / Cluster

    US West (N. California)

    ami-001a77544d24434ca

    Node / Cluster

    ami-0d6da9adc2aee302e

    Node / Cluster

    US West (Oregon)

    ami-0a5f8b95a3292ee9f

    Node / Cluster

    ami-0c0ada0f25ac9046e

    Node / Cluster

  2. 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.

  3. 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.

  4. 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.

  5. Tag your instance.

  6. Click Launch Cluster. You now have a running ScyllaDB cluster on EC2.

  7. 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?

PREVIOUS
Install ScyllaDB
NEXT
Launch ScyllaDB on GCP
  • Create an issue
  • Edit this page

On this page

  • Launch ScyllaDB on AWS
    • Launching Instances from ScyllaDB AMI
    • Next Steps
ScyllaDB Manual
Search Ask AI
  • 2025.1
    • master
    • 2026.3
    • 2026.2
    • 2026.1
    • 2025.4
    • 2025.3
    • 2025.2
    • 2025.1
  • Getting Started
    • Install ScyllaDB
      • Launch ScyllaDB on AWS
      • Launch ScyllaDB on GCP
      • Launch ScyllaDB on Azure
      • ScyllaDB Web Installer for Linux
      • Install ScyllaDB Linux Packages
      • Run ScyllaDB in Docker
      • Install ScyllaDB Without root Privileges
      • Air-gapped Server Installation
      • ScyllaDB Housekeeping and how to disable it
      • ScyllaDB Developer Mode
    • Configure ScyllaDB
    • ScyllaDB Configuration Reference
    • ScyllaDB Requirements
      • System Requirements
      • OS Support
      • Cloud Instance Recommendations
      • ScyllaDB in a Shared Environment
    • Migrate to ScyllaDB
      • Migration Process from Cassandra to ScyllaDB
      • ScyllaDB and Apache Cassandra Compatibility
      • Migration Tools Overview
    • Integration Solutions
      • Integrate ScyllaDB with Spark
      • Integrate ScyllaDB with KairosDB
      • Integrate ScyllaDB with Presto
      • Integrate ScyllaDB with Elasticsearch
      • Integrate ScyllaDB with Kubernetes
      • Integrate ScyllaDB with the JanusGraph Graph Data System
      • Integrate ScyllaDB with DataDog
      • Integrate ScyllaDB with Kafka
      • Integrate ScyllaDB with IOTA Chronicle
      • Integrate ScyllaDB with Spring
      • Shard-Aware Kafka Connector for ScyllaDB
      • Install ScyllaDB with Ansible
      • Integrate ScyllaDB with Databricks
      • Integrate ScyllaDB with Jaeger Server
      • Integrate ScyllaDB with MindsDB
  • ScyllaDB for Administrators
    • Administration Guide
    • Procedures
      • Cluster Management
      • Backup & Restore
      • Change Configuration
      • Maintenance
      • Best Practices
      • Benchmarking ScyllaDB
      • Migrate from Cassandra to ScyllaDB
      • Disable Housekeeping
    • Security
      • ScyllaDB Security Checklist
      • Enable Authentication
      • Enable and Disable Authentication Without Downtime
      • Creating a Custom Superuser
      • Generate a cqlshrc File
      • Reset Authenticator Password
      • Enable Authorization
      • Grant Authorization CQL Reference
      • Certificate-based Authentication
      • Role Based Access Control (RBAC)
      • ScyllaDB Auditing Guide
      • Encryption: Data in Transit Client to Node
      • Encryption: Data in Transit Node to Node
      • Generating a self-signed Certificate Chain Using openssl
      • Configure SaslauthdAuthenticator
      • Encryption at Rest
      • LDAP Authentication
      • LDAP Authorization (Role Management)
    • Admin Tools
      • Nodetool Reference
      • CQLSh
      • Admin REST API
      • Tracing
      • ScyllaDB SStable
      • ScyllaDB Types
      • SSTableLoader
      • cassandra-stress
      • SSTabledump
      • SSTableMetadata
      • ScyllaDB Logs
      • Seastar Perftune
      • Virtual Tables
      • Reading mutation fragments
      • Maintenance socket
      • Maintenance mode
      • Task manager
    • ScyllaDB Monitoring Stack
    • ScyllaDB Operator
    • ScyllaDB Manager
    • Upgrade Procedures
      • About Upgrade
      • Upgrade Guides
    • System Configuration
      • System Configuration Guide
      • scylla.yaml
      • ScyllaDB Snitches
    • Benchmarking ScyllaDB
    • ScyllaDB Diagnostic Tools
  • ScyllaDB for Developers
    • Develop with ScyllaDB
    • Tutorials and Example Projects
    • Learn to Use ScyllaDB
    • ScyllaDB Alternator
    • ScyllaDB Drivers
  • CQL Reference
    • CQLSh: the CQL shell
    • Appendices
    • Compaction
    • Consistency Levels
    • Consistency Level Calculator
    • Data Definition
    • Data Manipulation
      • SELECT
      • INSERT
      • UPDATE
      • DELETE
      • BATCH
    • Data Types
    • Definitions
    • Global Secondary Indexes
    • Expiring Data with Time to Live (TTL)
    • Functions
    • Wasm support for user-defined functions
    • JSON Support
    • Materialized Views
    • Non-Reserved CQL Keywords
    • Reserved CQL Keywords
    • DESCRIBE SCHEMA
    • Service Levels
    • ScyllaDB CQL Extensions
  • Alternator: DynamoDB API in Scylla
    • Getting Started With ScyllaDB Alternator
    • ScyllaDB Alternator for DynamoDB users
    • Alternator-specific APIs
  • Features
    • Lightweight Transactions
    • Global Secondary Indexes
    • Local Secondary Indexes
    • Materialized Views
    • Counters
    • Change Data Capture
      • CDC Overview
      • The CDC Log Table
      • Basic operations in CDC
      • CDC Streams
      • CDC Stream Generations
      • Querying CDC Streams
      • Advanced column types
      • Preimages and postimages
      • Data Consistency in CDC
    • Workload Attributes
    • Workload Prioritization
  • ScyllaDB Architecture
    • Data Distribution with Tablets
    • ScyllaDB Ring Architecture
    • ScyllaDB Fault Tolerance
    • Consistency Level Console Demo
    • ScyllaDB Anti-Entropy
      • ScyllaDB Hinted Handoff
      • ScyllaDB Read Repair
      • ScyllaDB Repair
    • SSTable
      • ScyllaDB SSTable - 2.x
      • ScyllaDB SSTable - 3.x
    • Compaction Strategies
    • Raft Consensus Algorithm in ScyllaDB
    • Zero-token Nodes
  • Troubleshooting ScyllaDB
    • Errors and Support
      • Report a ScyllaDB problem
      • Error Messages
      • Change Log Level
    • ScyllaDB Startup
      • Ownership Problems
      • ScyllaDB will not Start
      • ScyllaDB Python Script broken
    • Upgrade
      • Inaccessible configuration files after ScyllaDB upgrade
    • Cluster and Node
      • Handling Node Failures
      • Failure to Add, Remove, or Replace a Node
      • Failed Decommission Problem
      • Cluster Timeouts
      • Node Joined With No Data
      • NullPointerException
      • Failed Schema Sync
    • Data Modeling
      • ScyllaDB Large Partitions Table
      • ScyllaDB Large Rows and Cells Table
      • Large Partitions Hunting
      • Failure to Update the Schema
    • Data Storage and SSTables
      • Space Utilization Increasing
      • Disk Space is not Reclaimed
      • SSTable Corruption Problem
      • Pointless Compactions
      • Limiting Compaction
    • CQL
      • Time Range Query Fails
      • COPY FROM Fails
      • CQL Connection Table
    • ScyllaDB Monitor and Manager
      • Manager and Monitoring integration
      • Manager lists healthy nodes as down
    • Installation and Removal
      • Removing ScyllaDB on Ubuntu breaks system packages
  • Knowledge Base
    • Upgrading from experimental CDC
    • Compaction
    • Consistency in ScyllaDB
    • Counting all rows in a table is slow
    • CQL Query Does Not Display Entire Result Set
    • When CQLSh query returns partial results with followed by “More”
    • Run ScyllaDB and supporting services as a custom user:group
    • Customizing CPUSET
    • Decoding Stack Traces
    • Snapshots and Disk Utilization
    • DPDK mode
    • Debug your database with Flame Graphs
    • Efficient Tombstone Garbage Collection in ICS
    • How to Change gc_grace_seconds for a Table
    • Gossip in ScyllaDB
    • Increase Permission Cache to Avoid Non-paged Queries
    • How does ScyllaDB LWT Differ from Apache Cassandra ?
    • Map CPUs to ScyllaDB Shards
    • ScyllaDB Memory Usage
    • NTP Configuration for ScyllaDB
    • Updating the Mode in perftune.yaml After a ScyllaDB Upgrade
    • POSIX networking for ScyllaDB
    • ScyllaDB consistency quiz for administrators
    • Recreate RAID devices
    • How to Safely Increase the Replication Factor
    • ScyllaDB and Spark integration
    • Increase ScyllaDB resource limits over systemd
    • ScyllaDB Seed Nodes
    • How to Set up a Swap Space
    • ScyllaDB Snapshots
    • ScyllaDB payload sent duplicated static columns
    • Stopping a local repair
    • System Limits
    • How to flush old tombstones from a table
    • Time to Live (TTL) and Compaction
    • ScyllaDB Nodes are Unresponsive
    • Update a Primary Key
    • Using the perf utility with ScyllaDB
    • Configure ScyllaDB Networking with Multiple NIC/IP Combinations
  • Reference
    • AWS Images
    • Azure Images
    • GCP Images
    • Configuration Parameters
    • Glossary
    • Limits
    • API Reference
    • Metrics
  • ScyllaDB FAQ
  • 2024.2 and earlier documentation
Docs Tutorials University Contact Us About Us
© 2026, ScyllaDB. All rights reserved. | Terms of Service | Privacy Policy | ScyllaDB, and ScyllaDB Cloud, are registered trademarks of ScyllaDB, Inc.
Last updated on 02 Sep 2026.
Powered by Sphinx 9.1.0 & ScyllaDB Theme 1.9.3