Guide

Cassandra Endpoint

Cassandra endpoints connect Gateway to Apache Cassandra-compatible clusters for governed wide-column data access and operational workflows.

Endpoint Kind

Use cassandra as the endpoint kind when creating this endpoint through the API or dashboard.

What Gateway Uses Cassandra Endpoints For

Query Cassandra keyspaces through a governed endpoint.
Centralize credential handling and access control.
Inspect cluster and keyspace metadata for operational planning.
Combine Cassandra data with SQL, search, observability, and LLM workflows.

Basic Endpoint Shape

json

{
  "endpoint": "cassandra-prod",
  "kind": "cassandra",
  "config": {
    "read_conn": {
      "hosts": "cassandra-1.internal,cassandra-2.internal",
      "port": 9042,
      "keyspace": "app",
      "user": "app_user",
      "password": "secret"
    }
  },
  "description": "Production Cassandra cluster"
}

Create it with the endpoint API:

bash

curl -sS -X POST "$EDEN/endpoints" \
  -H "$AUTH_HEADER" \
  -H "Content-Type: application/json" \
  -d '{
    "endpoint": "cassandra-prod",
    "kind": "cassandra",
    "config": {
      "read_conn": {
        "hosts": "cassandra-1.internal,cassandra-2.internal",
        "port": 9042,
        "keyspace": "app",
        "user": "app_user",
        "password": "secret"
      }
    },
    "description": "Production Cassandra cluster"
  }'

Configuration Fields

Field	Purpose
`hosts`	One or more contact points.
`port`	Native protocol port, usually `9042`.
`keyspace`	Default keyspace.
`user`	Optional username.
`password`	Optional password.

Operating Notes

Confirm contact points, datacenter awareness, and consistency expectations before production use.
Scope credentials to the keyspaces and tables Gateway should access.
Watch read fanout and large partition behavior when exposing Cassandra data to tools or agents.