Get started with Aiven for Apache Cassandra®

End of life

Aiven for Apache Cassandra® is approaching its end of life. You can create new services until November 30, 2025. Existing services will continue to run until December 31, 2025, at which point they will be deleted. To avoid data loss and service disruptions, migrate your data out of Aiven for Apache Cassandra® before December 31, 2025.

Learn more

Start using Aiven for Apache Cassandra® by creating and configuring a service, connecting to it, and playing with sample data.

Prerequisites

You need some of the following dev tools for different Aiven for Apache Cassandra operations:

• Apache Cassandra and the cqlsh client
• Access to the Aiven Console
• Aiven Provider for Terraform
• Aiven Operator for Kubernetes®

Create an Aiven for Apache Cassandra® service

Console

1. In your project, click Services.

2. Click Create service.

3. Select Apache Cassandra®.

4. Enter a name for your service.

   important

   You cannot change the name after you create the service.

   You can fork the service with a new name instead.

5. Optional: Add tags.

6. Select the cloud provider, region, and plan.

   note

   Available plans and pricing for the same service can vary between cloud providers and regions.

7. Optional: Add disk storage.

8. In the Service summary, click Create service.

The status of the service is Rebuilding during its creation. When the status is Running, you can start using the service. This typically takes couple of minutes and can vary between cloud providers and regions.

Terraform

Create an Aiven for Apache Cassandra service using the Aiven Provider for Terraform.

1. Create a token.

2. Create the cassandra-sample.tf file for the aiven provider configuration and the aiven_cassandra resource.

   variable "aiven_token" {
     type = string
   }
   
   variable "aiven_project_name" {
     type = string
   }
   
   terraform {
     required_providers {
       aiven = {
         source  = "aiven/aiven"
         version = ">=4.0.0, <5.0.0"
       }
     }
   }
   
   provider "aiven" {
     api_token = var.aiven_token
   }
   
   resource "aiven_cassandra" "example_cassandra" {
     project                 = var.aiven_project_name
     cloud_name              = "google-europe-west1"
     plan                    = "startup-4"
     service_name            = "cassandra-sample"
     maintenance_window_dow  = "friday"
     maintenance_window_time = "23:00:00"
     termination_protection  = false
   
     cassandra_user_config {
       migrate_sstableloader = true
       service_log           = false
     }
   }
   
   output "cassandra_service_host" {
     value = aiven_cassandra.example_cassandra.service_host
   }
   
   output "cassandra_service_port" {
     value = aiven_cassandra.example_cassandra.service_port
   }
   
   output "cassandra_service_username" {
     value = aiven_cassandra.example_cassandra.service_username
   }
   
   output "cassandra_service_password" {
     value     = aiven_cassandra.example_cassandra.service_password
     sensitive = true
   }

3. Create the terraform.tfvars file for assigning actual values to your previously declared variables.

   aiven_token    = "AIVEN_TOKEN"
   aiven_project_name = "PROJECT_NAME"

4. Run terraform init > terraform plan > terraform apply.

5. Store Terraform outputs in environment variables so that they can be used for connecting:

   CASSANDRA_HOST="$(terraform output -raw cassandra_service_host)"
   CASSANDRA_PORT="$(terraform output -raw cassandra_service_port)"
   CASSANDRA_USER="$(terraform output -raw cassandra_service_username)"
   CASSANDRA_PASSWORD="$(terraform output -raw cassandra_service_password)"

The resource can stay in the REBUILDING state for a couple of minutes. Once the state changes to RUNNING, you are ready to access it.

Kubernetes

Create an Aiven for Apache Cassandra service using the Aiven Operator for Kubernetes.

1. Get authenticated and authorized.

2. Create file cassandra-sample.yaml with the following content:

   apiVersion: aiven.io/v1alpha1
   kind: Cassandra
   metadata:
     name: cassandra-sample
   spec:
     authSecretRef:
       name: aiven-token
       key: token
   
     connInfoSecretTarget:
       name: cassandra-secret
   
     userConfig:
       migrate_sstableloader: true
       service_log: false
   
     project: PROJECT_NAME
     cloudName: google-europe-west1
     plan: startup-4
   
     maintenanceWindowDow: friday
     maintenanceWindowTime: 23:00:00

3. Create the service by applying the configuration:

   kubectl apply -f cassandra-sample.yaml

4. Review the resource you created with the following command:

   kubectl get cassandras cassandra-sample

The resource can stay in the REBUILDING state for a couple of minutes. Once the state changes to RUNNING, you are ready to access it.

Configure the service

You can change your service settings by updating the service configuration.

tip

See configuration options in Advanced parameters for Aiven for Apache Cassandra®.

Console

1. Select the new service from the list of services on the Services page.
2. On the Overview page, select Service settings from the sidebar.
3. In the Advanced configuration section, make changes to the service configuration.

Terraform

note

Your changes can force the recreation of the aiven_cassandra resource.

See attributes available for the aiven_cassandra resource in the Aiven Provider for Terraform® documentation.

1. Update the aiven_cassandra resource in the cassandra-sample.tf file:

   • Add service_log = true and termination_protection = true.
   • Update maintenance_window_dow = "sunday" and maintenance_window_time = "22:00:00".

   variable "aiven_token" {
     type = string
   }
   
   variable "aiven_project_name" {
     type = string
   }
   
   terraform {
     required_providers {
       aiven = {
         source  = "aiven/aiven"
         version = ">=4.0.0, <5.0.0"
       }
     }
   }
   
   provider "aiven" {
     api_token = var.aiven_token
   }
   
   resource "aiven_cassandra" "example_cassandra" {
     project                 = var.aiven_project_name
     cloud_name              = "google-europe-west1"
     plan                    = "startup-4"
     service_name            = "cassandra-sample"
     maintenance_window_dow  = "sunday"
     maintenance_window_time = "22:00:00"
     termination_protection  = true
   
     cassandra_user_config {
       migrate_sstableloader = true
       service_log = true
     }
   }
   
   output "cassandra_service_host" {
     value = aiven_cassandra.example_cassandra.service_host
   }
   
   output "cassandra_service_port" {
     value = aiven_cassandra.example_cassandra.service_port
   }
   
   output "cassandra_service_username" {
   value = aiven_cassandra.example_cassandra.service_username
   }
   
   output "cassandra_service_password" {
     value     = aiven_cassandra.example_cassandra.service_password
     sensitive = true
   }

2. Run terraform plan > terraform apply.

The resource can stay in the REBUILDING state for a couple of minutes. Once the state changes to RUNNING, you are ready to access it.

Kubernetes

note

Your changes can force the recreation of the aiven_cassandra resource.

See available configuration options in Aiven Operator for Kubernetes®: Cassandra.

1. Update file cassandra-sample.yaml:

   • Add service_log: true and terminationProtection: true.
   • Update maintenanceWindowDow: sunday and maintenanceWindowTime: 22:00:00.

   apiVersion: aiven.io/v1alpha1
   kind: Cassandra
   metadata:
     name: cassandra-sample
   spec:
     authSecretRef:
       name: aiven-token
       key: token
   
     connInfoSecretTarget:
       name: cassandra-secret
   
     userConfig:
       migrate_sstableloader: true
       service_log: true
   
     project: PROJECT_NAME
     cloudName: google-europe-west1
     plan: startup-4
   
     maintenanceWindowDow: sunday
     maintenanceWindowTime: 22:00:00
     terminationProtection: true

2. Update the service by applying the configuration:

   kubectl apply -f cassandra-sample.yaml

3. Review the resource you updated with the following command:

   kubectl describe cassandra.aiven.io cassandra-sample

The resource can stay in the REBUILDING state for a couple of minutes. Once the state changes to RUNNING, you are ready to access it.

Connect to the service

Console

1. Log in to the Aiven Console, and go to your organization > project > Aiven for Apache Cassandra service.

2. On the Overview page of your service, click Quick connect.

3. In the Connect window, select a tool or language to connect to your service, follow the connection instructions, and click Done.

   # Sample command for connecting with the cqlsh client
   
   ./cqlsh --ssl -u USER_NAME -p PASSWORD HOST_NAME PORT_NUMBER

Terraform

Access your new service with the Apache Cassandra client using the environment variables assigned to Terraform outputs:

./cqlsh --ssl --host=$CASSANDRA_HOST --port=$CASSANDRA_PORT --user=$CASSANDRA_USER --password=$CASSANDRA_PASSWORD

cqlsh client

Connect to your new service with CLI using the the cqlsh client.

tip

Discover more tools for connecting to Aiven for Apache Cassandra in Connect to Aiven for Apache Cassandra®.

Create keyspaces and tables

Use cqlsh to create a keyspace and a table where you can insert your data next.

1. Create a keyspace, for example library:

   CREATE KEYSPACE IF NOT EXISTS library WITH REPLICATION = { 'class': 'NetworkTopologyStrategy', 'aiven': 3 };

   where aiven is the default datacenter name for Aiven for Apache Cassandra services.

2. Create a table within the library keyspace, for example book_tracker:

   CREATE TABLE IF NOT EXISTS library.book_tracker (book_id text PRIMARY KEY, item_count int, genre text, status text, last_update_timestamp timestamp);

Insert data

Use cqlsh to write data in the book_tracker table, for example:

INSERT INTO library.book_tracker (book_id, item_count, genre, status, last_update_timestamp) VALUES ('01234', 6, 'true_crime', 'available', toTimeStamp(now()));
INSERT INTO library.book_tracker (book_id, item_count, genre, status, last_update_timestamp) VALUES ('56789', 13, 'romance', 'unavailable', toTimeStamp(now()));
INSERT INTO library.book_tracker (book_id, item_count, genre, status, last_update_timestamp) VALUES ('12345', 55, 'spirituality_religions', 'available', toTimeStamp(now()));
INSERT INTO library.book_tracker (book_id, item_count, genre, status, last_update_timestamp) VALUES ('67890', 3, 'adventure', 'unavailable', toTimeStamp(now()));
INSERT INTO library.book_tracker (book_id, item_count, genre, status, last_update_timestamp) VALUES ('98765', 6, 'true_crime', 'available', '2024-08-01');
INSERT INTO library.book_tracker (book_id, item_count, genre, status, last_update_timestamp) VALUES ('98765', 22, 'history', 'available', '2024-08-01');
INSERT INTO library.book_tracker (book_id, item_count, genre, status, last_update_timestamp) VALUES ('87654', 4, 'psychology', 'unavailable', '2022-02-11');
INSERT INTO library.book_tracker (book_id, item_count, genre, status, last_update_timestamp) VALUES ('76543', 101, 'health', 'available', '2010-09-23');
INSERT INTO library.book_tracker (book_id, item_count, genre, status, last_update_timestamp) VALUES ('65432', 74, 'horror', 'unavailable', '2007-11-19');

tip

For importing large amount of data or for batch data load, see:

• Use DSBULK to load, unload, and count data
• Migrate to Aiven with the ZDM Proxy

Read data

Use cqlsh to read data from the book_tracker table, for example:

• SELECT * FROM library.book_tracker WHERE book_id = '01234';
  
  book_id | genre      | item_count | last_update_timestamp           | status
  --------+------------+------------+---------------------------------+----------
   01234  | true_crime |          6 | 2024-07-31 11:21:14.263000+0000 | available

• SELECT genre, item_count FROM library.book_tracker WHERE book_id IN ('01234', '12345');
  
  genre                  | item_count
  -----------------------+-----------
              true_crime |          6
  spirituality_religions |         55

• SELECT last_update_timestamp, status FROM library.book_tracker WHERE book_id IN ('01234', '12345', '98765', '87654');
  
  last_update_timestamp           | status
  --------------------------------+------------
  2024-07-31 11:21:14.263000+0000 |   available
  2024-07-31 11:24:20.373000+0000 |   available
  2022-02-11 00:00:00.000000+0000 | unavailable
  2024-08-01 00:00:00.000000+0000 |   available

Related pages

• Supported Aiven for Apache Cassandra versions
• Aiven for Apache Cassandra backups
• Cross-cluster replication