AWS Keyspaces Integration with Pega Helm Chart

General
, , , ,
1

Hello,

I am currently working on configuring Pega for my project, and I’m exploring the possibility of using AWS Keyspaces as the database backend instead of the Cassandra that deploys with the Pega Helm chart. I’ve made some changes in my configuration, and I would like to confirm whether this setup is appropriate.

Here is my current configuration:

cassandra:
  enabled: false

dds:
  externalNodes: "CASSANDRA_NODE_IPS"
  port: "9042"
  username: ""
  password: ""
  keyspacesPrefix: "dev01"
  trustStore: "/opt/pega/certs/cass-truststore.jks"
  keyStore: "/opt/pega/certs/cass-keystore.jks"
  extendedTokenAwarePolicy: true
  customRetryPolicy: true
  csvMetricsEnabled: false
  logMetricsEnabled: false
  # The external secret below contains passwords with the following keys: CASSANDRA_USERNAME, CASSANDRA_PASSWORD, CASSANDRA_TRUSTSTORE_PASSWORD, CASSANDRA_KEYSTORE_PASSWORD
  external_secret_name: "dev02-credentials-secret"

Could you please provide guidance on whether this configuration is suitable for integrating Pega with AWS Keyspaces? If there are any specific changes or considerations I need to keep in mind, please let me know.

Thank you for your assistance.

Best regards,

Josue Aquino

2

@JosueA99

A substitute for Cassandra cannot be used when installing Pega Customer Decision Hub on-premises.

Pega Customer Decision Hub uses Cassandra as the underlying storage system for the Decision Data Store (DDS) and only supports Cassandra distributions that are based on genuine Apache Cassandra.

Documentation can be found here:

https://docs.pega.com/bundle/customer-decision-hub/page/customer-decision-hub/install/deployment-requirements.html