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 2026.3 Launch ScyllaDB 2026.3 on AWS
For AI agents: a documentation index is available at https://docs.scylladb.com/manual/branch-2026.3/llms.txt. A Markdown version of this page is at https://docs.scylladb.com/manual/branch-2026.3/getting-started/install-scylla/launch-on-aws.md.

Launch ScyllaDB 2026.3 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.

    2026.3.6¶

    Region

    x86 AMI ID

    Launch x86

    ARM AMI ID

    Launch ARM

    Asia Pacific (Hyderabad)

    ami-0173b97bf7467e0fd

    Node / Cluster

    ami-0ff51a58b027cc36a

    Node / Cluster

    Africa (Cape Town)

    ami-045c5a394ae4e9c02

    Node / Cluster

    ami-0583fc0e84c2adb29

    Node / Cluster

    Asia Pacific (Mumbai)

    ami-0b3d131ba035cb0c3

    Node / Cluster

    ami-099f5eaf8bd8f4f4a

    Node / Cluster

    Europe (Stockholm)

    ami-03dc720d16d44e26e

    Node / Cluster

    ami-09e1445732c9f6185

    Node / Cluster

    Europe (Paris)

    ami-0c0a7b54979e8a4dd

    Node / Cluster

    ami-0766dcb37d0a85058

    Node / Cluster

    Europe (Milan)

    ami-06df2533e06ab870e

    Node / Cluster

    ami-07ae56fb1cc30204e

    Node / Cluster

    Europe (London)

    ami-0600c06b5476caed4

    Node / Cluster

    ami-0c4b9a5e39081c076

    Node / Cluster

    Europe (Ireland)

    ami-0ff5189f1ab5d1346

    Node / Cluster

    ami-09f6e6d8eda989d0d

    Node / Cluster

    Asia Pacific (Osaka)

    ami-068145b18b4cddcab

    Node / Cluster

    ami-068ec0dc0993a4cbd

    Node / Cluster

    Asia Pacific (Seoul)

    ami-0e68e0cbaed173193

    Node / Cluster

    ami-01355d41c3dfd7ffd

    Node / Cluster

    Asia Pacific (Tokyo)

    ami-0af9129649191964c

    Node / Cluster

    ami-053302ac92994b866

    Node / Cluster

    Israel (Tel Aviv)

    ami-0459579f6e8830c34

    Node / Cluster

    ami-02ce1a744debe5939

    Node / Cluster

    Canada (Central)

    ami-0d254f548d11f38cb

    Node / Cluster

    ami-015c649d6f9f88a13

    Node / Cluster

    South America (Sao Paulo)

    ami-0257158d95eaff18b

    Node / Cluster

    ami-0e5fc74016d9bb23c

    Node / Cluster

    Asia Pacific (Hong Kong)

    ami-01b0dd08b330a3813

    Node / Cluster

    ami-04e6de00c1d8a80de

    Node / Cluster

    Asia Pacific (Singapore)

    ami-08e29b420d392ff41

    Node / Cluster

    ami-0f8e3ea86501f365a

    Node / Cluster

    Asia Pacific (Sydney)

    ami-03164758bb93e1839

    Node / Cluster

    ami-016d9f60908345eea

    Node / Cluster

    Europe (Frankfurt)

    ami-01a61107a73ccc008

    Node / Cluster

    ami-0fca3437d4dd6e3f9

    Node / Cluster

    US East (N. Virginia)

    ami-092e9afcd9fc7f2d9

    Node / Cluster

    ami-0d07cacf564f05bdc

    Node / Cluster

    US East (Ohio)

    ami-01b07e5ee886047f4

    Node / Cluster

    ami-08d35fc2953d2d3fb

    Node / Cluster

    US West (N. California)

    ami-0b7e7b55e5f7abb3b

    Node / Cluster

    ami-0d7587d587016d328

    Node / Cluster

    US West (Oregon)

    ami-075825edaf31b67c0

    Node / Cluster

    ami-03261bf3bc591d991

    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 2026.3
NEXT
Launch ScyllaDB 2026.3 on GCP
  • Create an issue
  • Edit this page

On this page

  • Launch ScyllaDB 2026.3 on AWS
    • Launching Instances from ScyllaDB AMI
    • Next Steps
ScyllaDB Manual
Search Ask AI
  • 2026.3
    • master
    • 2026.4
    • 2026.3
    • 2026.2
    • 2026.1
    • 2025.4
    • 2025.3
    • 2025.2
    • 2025.1
  • Getting Started
    • Install ScyllaDB 2026.3
      • Launch ScyllaDB 2026.3 on AWS
      • Launch ScyllaDB 2026.3 on GCP
      • Launch ScyllaDB 2026.3 on Azure
      • Launch ScyllaDB 2026.3 on Oracle Cloud Infrastructure (OCI)
      • ScyllaDB Web Installer for Linux
      • Install ScyllaDB 2026.3 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 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)
      • Software Bill Of Materials (SBOM)
    • Admin Tools
      • Nodetool Reference
      • CQLSh
      • Admin REST API
      • Tracing
      • ScyllaDB SStable
      • ScyllaDB SStable Script API
      • ScyllaDB Types
      • SSTableLoader
      • cassandra-stress
      • ScyllaDB Logs
      • Seastar Perftune
      • Virtual Tables
      • Reading mutation fragments
      • Maintenance socket
      • Maintenance mode
      • Task manager
    • ScyllaDB Monitoring Stack
    • ScyllaDB Operator
    • ScyllaDB Manager
    • Upgrade Procedures
      • Upgrade Guides
    • System Configuration
      • System Configuration Guide
      • scylla.yaml
      • ScyllaDB Snitches
      • Configuration Parameters
    • 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
    • Reserved CQL Keywords and Types (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
    • CQL Guardrails
    • Wasm support for user-defined functions
    • JSON Support
    • Materialized Views
    • DESCRIBE SCHEMA
    • Service Levels
    • ScyllaDB CQL Extensions
  • Alternator: DynamoDB API in ScyllaDB
    • Getting Started With ScyllaDB Alternator
    • ScyllaDB Alternator for DynamoDB users
    • Alternator-specific APIs
    • Reducing network costs in Alternator
    • Alternator Vector Search
  • 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 Changes
      • Querying CDC Streams
      • Advanced column types
      • Preimages and postimages
      • Data Consistency in CDC
    • Workload Attributes
    • Workload Prioritization
    • Backup and Restore
    • Incremental Repair
    • Automatic Repair
    • Vector Search
    • Full-Text Search
  • 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
    • 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
    • How does ScyllaDB LWT Differ from Apache Cassandra ?
    • Map CPUs to ScyllaDB Shards
    • ScyllaDB Memory Usage
    • NTP Configuration for ScyllaDB
    • 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
      • Authorization Cache
      • Cache Service
      • Collectd
      • Column Family
      • Commit Log
      • Compaction Manager
      • Endpoint Snitch Info
      • Error Injection
      • Failure Detector
      • Gossiper
      • Hinted Handoff
      • LSA
      • Messaging Service
      • Raft
      • Storage Proxy
      • Storage Service
      • Stream Manager
      • System
      • Task Manager Test
      • Task Manager
      • Tasks
    • 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 21 Jan 2026.
Powered by Sphinx 9.1.1 & ScyllaDB Theme 1.10.0