Skip to main content
This guide provides the configuration parameters for connecting RisingWave to the object storage backend for your Apache Iceberg data. These parameters are used in the WITH clause when creating an Iceberg source, sink, or connection.

S3-compatible storage

These parameters configure the connection to an S3-compatible storage system, such as AWS S3 or MinIO, where your Iceberg data files are stored.
In RisingWave Cloud, you have two options:
  • Provide s3.access.key and s3.secret.key, or
  • Use IAM role delegation: grant S3 permissions to your own IAM role, allow the RisingWave Cloud tenant role to assume it, then set s3.iam_role_arn = '<your_role_arn>' and enable_config_load = true. See Set up IAM role assume for a step-by-step guide, including how to retrieve the required IAM role ARN from the Cloud metadata page.
If you use a REST catalog with vended credentials (vended_credentials = true), you can omit S3 credentials here because the catalog server provides temporary credentials.In self-hosted deployments, if you want to rely on the AWS SDK default credential chain (for example, environment variables or an EC2 instance profile), set enable_config_load = true and omit s3.access.key/s3.secret.key.

Google Cloud Storage (GCS)

These parameters configure the connection to Google Cloud Storage.
Support for GCS was added in RisingWave v2.3.0.
Example

Azure Blob Storage

These parameters configure the connection to Azure Blob Storage.
Support for Azure Blob Storage was added in RisingWave v2.4.0.
Example

Azure Data Lake Storage Gen2 (ADLS)

These parameters configure the connection to Azure Data Lake Storage Gen2.
Support for ADLS was added in RisingWave v2.5.0. ADLS can only be used with REST catalog.
Example