Limitations for data sharing (preview) - Amazon Redshift
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Limitations for data sharing (preview)

This is prerelease documentation for the multi-data warehouse writes through data sharing feature for Amazon Redshift, which is available in public preview in the PREVIEW_2023 track. The documentation and the feature are both subject to change. We recommend that you use this feature only with test clusters, and not in production environments. For preview terms and conditions, see Beta Service Participation in Amazon Service Terms.

If you haven't created a datashare yet on the preview track, go to Sharing both read and write data within an Amazon account or across accounts to get started.

The following are limitations when working with datashares in Redshift:

  • Multi-warehouse writes through data sharing is not currently available on ra3.xlplus clusters. To use this feature, create clusters with the following node types:

    • ra3.4xl

    • ra3.16xl

    It also works with Amazon Redshift Serverless workgroups with the preview track.

  • For cross-account and cross-Region data sharing, both the producer and consumer clusters and serverless namespaces must be encrypted. This is for security purposes. However, they don't need to share the same encryption key.

  • You can only share SQL UDFs through datashares. Python and Lambda UDFs aren't supported.

  • If the producer database has specific collation, use the same collation settings for the consumer database.

  • Redshift doesn't support adding external schemas, tables, or late-binding views on external tables to datashares.

  • Redshift doesn't support nested SQL user-defined functions on producer clusters.

  • Redshift doesn't support sharing tables with interleaved sort keys and views that refer to tables with interleaved sort keys.

  • Consumers can't add datashare objects to another datashare. Additionally, consumers can't add views referencing datashare objects to another datashare.

  • Redshift doesn't support accessing a datashare object which had a concurrent DDL occur between the Prepare and Execute of the access.

  • Redshift doesn't support sharing stored procedures through datashares.

For more information about data-sharing limitations, see Requirements and limitations for datasharing in preview.