Skip to main content
The RisingWave engine requires a metadata store to persist its catalog and runtime metadata. During Private Preview, StreamNative provides this store with Amazon RDS for PostgreSQL. This metadata store is engine infrastructure. It is separate from the logical databases created by SQLCatalog and is not a PostgreSQL endpoint for user queries.

​
Resource model

StreamNative provisions one shared RDS for PostgreSQL instance for each SQLWorkspace-enabled AWS placement. When you create a SQLWorkspace, StreamNative creates a dedicated PostgreSQL database, role, and credentials for that workspace on the shared instance. This model provides:
  • A durable metadata backend shared at the placement level.
  • A separate database and role for each SQLWorkspace.
  • Automatically managed credentials that are not exposed as a user connection workflow.
The SQLWorkspace engine uses the dedicated database to store definitions and internal metadata for sources, tables, materialized views, users, and other engine objects. Pulsar and Kafka event data remains in the source cluster; it is not copied into RDS as the topic data store.

​
Security and connectivity

StreamNative places the RDS instance in private AWS subnets and does not expose it publicly. Engine connections use PostgreSQL over TLS. Storage encryption, backups, maintenance, and deletion protection are managed as part of the SQLWorkspace infrastructure. You do not need to provide RDS credentials or connect to this instance. Use SQL Studio or the SQLWorkspace native PostgreSQL endpoint to query the RisingWave engine.
Amazon RDS for PostgreSQL is the only managed SQLWorkspace metadata-store provider supported during Private Preview. Metadata stores on Azure, Google Cloud, Alibaba Cloud, or other providers are not supported.