# Running on Amazon Keyspaces
**URL:** https://community.temporal.io/t/running-on-amazon-keyspaces/159
**Category:** Community Support
**Tags:** cassandra, keyspaces, aws
**Created:** [July 13, 2020, 6:20pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159 "2020-07-13T18:20:31Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@Jared\_Sutherland](https://community.temporal.io/u/Jared_Sutherland)
#### Post date: [July 13, 2020, 6:20pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/1 "2020-07-13T18:20:32Z")
Curious if anyone has been running Temporal with Amazon Keyspaces vs. managing their own Cassandra cluster? I know there is some specifics around the authentication around DataStax.
---
### Author:  [@markmark](https://community.temporal.io/u/markmark)
#### Post date: [July 13, 2020, 6:22pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/2 "2020-07-13T18:22:54Z")
This a great question, thank you. I casually tested Temporal + Amazon Keyspaces and it didn’t work — we need to do a bit of work to enable this use case.
I don’t know what our roadmap plans are for this work (cc: @ryland).
---
### Author:  [@ryland](https://community.temporal.io/u/ryland)
#### Post date: [July 13, 2020, 6:27pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/3 "2020-07-13T18:27:44Z")
We’ve had a few requests for keyspaces so this is something we definitely want to support and I’m actively tracking it. Right now it seems like a few off the shelf hosted Cassandra solutions aren’t actually as compatible as we hoped so as Mark said, there is considerable work.
---
### Author:  [@venkatp](https://community.temporal.io/u/venkatp)
#### Post date: [October 15, 2020, 5:52pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/4 "2020-10-15T17:52:44Z")
Hello, is there any update on supporting AWS Keyspace on temporal. One first thing is AWS keyspace does not support creating TYPE on the cassandra table which temporal has. There might be other discrepancies too. As of now, can we assume that temporal cannot be used with AWS Keyspaces?
---
### Author:  [@maxim](https://community.temporal.io/u/maxim)
#### Post date: [October 15, 2020, 6:56pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/5 "2020-10-15T18:56:04Z")
As of know it does not run on AWS Keyspaces. We will monitor their progress and add support as soon as it is feasible.
---
### Author:  [@andrei](https://community.temporal.io/u/andrei)
#### Post date: [October 26, 2020, 9:44am UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/6 "2020-10-26T09:44:17Z")
At this moment is seems that the missing feature in Keyspaces is batching LWTs. Are you aware of any other missing features that Temporal makes use of?
We would like to make a request to AWS to add the features required by Temporal to Keyspaces, hence the interest in the topic.
---
### Author:  [@maxim](https://community.temporal.io/u/maxim)
#### Post date: [October 26, 2020, 2:46pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/7 "2020-10-26T14:46:54Z")
My guess is that Keyspaces are implemented on top of DynamoDB. And DynamoDB itself doesn’t really support multikey transactions.
---
### Author:  [@andrei](https://community.temporal.io/u/andrei)
#### Post date: [October 27, 2020, 6:53am UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/8 "2020-10-27T06:53:57Z")
It is my impression that Keyspaces runs on top of Cassandra. In the past (~1year), AWS offered a managed Cassandra service as well, but they killed it and moved to offering it in serverless mode.
They list the key differences with Cassandra [here](https://docs.aws.amazon.com/keyspaces/latest/devguide/functional-differences.html#functional-differences.light-transactions). So it seems that they actually support batching unconditional `INSERT`, `UPDATE`, or `DELETE` commands. What they do not support is batching `LWTs`.
Additionally, they do not support all the consistency levels, such as `ALL` or `SERIAL`, but they do support `LOCAL_QUORUM`. Ideally the latter would be enough, as it would also be more performant.
---
### Author:  [@maledesma](https://community.temporal.io/u/maledesma)
#### Post date: [May 22, 2021, 2:30pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/9 "2021-05-22T14:30:47Z")
Any update on supporting AWS Keyspaces?
---
### Author:  [@maxim](https://community.temporal.io/u/maxim)
#### Post date: [May 22, 2021, 4:47pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/10 "2021-05-22T16:47:34Z")
We didn’t hear about any new features in AWS Keyspaces that might allow running on them.
---
### Author:  [@joebowbeer](https://community.temporal.io/u/joebowbeer)
#### Post date: [October 18, 2021, 11:02pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/11 "2021-10-18T23:02:50Z")
Also see [Try to run temporal on top of Amazon Keyspaces · Issue #328 · temporalio/temporal · GitHub](https://github.com/temporalio/temporal/issues/328)
---
### Author:  [@David\_Andrzejek](https://community.temporal.io/u/David_Andrzejek)
#### Post date: [March 25, 2022, 5:04am UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/12 "2022-03-25T05:04:20Z")
If you want to run Temporal on AWS but don’t want to operate Cassandra, you can use [astra.DataStax.com](http://astra.DataStax.com)… astra is Cassandra as a service on AWS/GCP/Azure and available via marketplaces. Or you can just get temporal as a service from Temporal.
Disclosure: I work for DataStax.
---
### Author:  [@Alexander\_Kulik](https://community.temporal.io/u/Alexander_Kulik)
#### Post date: [August 26, 2024, 7:26pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/13 "2024-08-26T19:26:06Z")
Hello all! any update?
---
### Author:  [@maxim](https://community.temporal.io/u/maxim)
#### Post date: [August 27, 2024, 4:35am UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/14 "2024-08-27T04:35:09Z")
Did keyspaces implement proper transactions?
---
### Author:  [@QuangNgo](https://community.temporal.io/u/QuangNgo)
#### Post date: [March 17, 2025, 9:39am UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/15 "2025-03-17T09:39:29Z")
@maxim I think they support LWT now, would that be enough?
> **[Functional differences: Amazon Keyspaces vs. Apache Cassandra - Amazon...](https://docs.aws.amazon.com/keyspaces/latest/devguide/functional-differences.html#functional-differences.light-transactions)**
>
> Learn about the key functional differences between Apache Cassandra and Amazon Keyspaces, and how these might affect your workloads when you migrate.
---
### Author:  [@maxim](https://community.temporal.io/u/maxim)
#### Post date: [March 17, 2025, 5:19pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/16 "2025-03-17T17:19:38Z")
They still don’t support batches. LWT without batches is not enough.
---
### Author:  [@pdaga2](https://community.temporal.io/u/pdaga2)
#### Post date: [March 27, 2025, 5:25pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/17 "2025-03-27T17:25:34Z")
Is the absence of the Logged Batches feature the only limitation preventing its use, or are there other constraints as well? Additionally, what thresholds does Temporal require for Logged Batches?
---
### Author:  [@maxim](https://community.temporal.io/u/maxim)
#### Post date: [March 27, 2025, 7:07pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/18 "2025-03-27T19:07:15Z")
We don’t know, as discrepancies between implementations can be very subtle. The Logged Batches is the big one. But it might be possible that there are many other incompatibilities.
---
### Author:  [@Ninglin](https://community.temporal.io/u/Ninglin)
#### Post date: [February 11, 2026, 9:27am UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/19 "2026-02-11T09:27:26Z")
I believe AWS Keyspaces support logged batches since November 2025. Source: [Amazon Keyspaces now supports logged batches for atomic, multi-statement operations | AWS Database Blog](https://aws.amazon.com/blogs/database/amazon-keyspaces-now-supports-logged-batches-for-atomic-multi-statement-operations/)
---
### Author:  [@Ninglin](https://community.temporal.io/u/Ninglin)
#### Post date: [February 12, 2026, 12:05pm UTC](https://community.temporal.io/t/running-on-amazon-keyspaces/159/20 "2026-02-12T12:05:31Z")
Update on this, with the most recent version, temporal is still not compatible with keyspaces due to the CREATE INDEX not being supported.
The `update-default-store` schema container is failing with: ”Unable to update CQL schema. {“error”: “error executing statement: Unsupported statement: org.apache.cassandra.cql3.statements.CreateIndexStatement@72cf23a9”, “logging-call-at”: “/home/runner/work/docker-builds/docker-builds/temporal/tools/cassandra/handler.go:61”}”