Considerations for data sharing with Amazon Web Services Data Exchange in Amazon Redshift - 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).

Amazon Redshift will no longer support the creation of new Python UDFs starting November 1, 2025. If you would like to use Python UDFs, create the UDFs prior to that date. Existing Python UDFs will continue to function as normal. For more information, see the blog post .

Considerations for data sharing with Amazon Web Services Data Exchange in Amazon Redshift

When using Amazon Web Services Data Exchange for Amazon Redshift, consider the following:

  • Both producers and consumers must use the RA3 instance types to use Amazon Redshift datashares. Producers must use the RA3 instance types with the latest Amazon Redshift cluster version.

  • Both the producer and consumer clusters must be encrypted.

  • You must be registered as an Amazon Web Services Data Exchange provider to list products on Amazon Web Services Data Exchange, including products that contain Amazon Web Services Data Exchange datashares. For more information, see Getting started as a provider.

  • You don't need to be a registered Amazon Web Services Data Exchange provider to find, subscribe to, and query Amazon Redshift data through Amazon Web Services Data Exchange.

  • To control access to your data, create Amazon Web Services Data Exchange datashares with the publicly accessible setting turned on. To alter an Amazon Web Services Data Exchange datashare to turn off the publicly accessible setting, set the session variable to allow ALTER DATASHARE SET PUBLICACCESSIBLE FALSE. For more information, see ALTER DATASHARE usage notes.

  • Producers can't manually add or remove consumers from Amazon Web Services Data Exchange datashares because access to the datashares is granted based on having an active subscription to an Amazon Web Services Data Exchange product that contains the Amazon Web Services Data Exchange datashare.

  • Producers can't view the SQL queries that consumers run. They can only view metadata, such as the number of queries or the objects consumers query, through Amazon Redshift tables that only the producer can access. For more information, see Monitoring and auditing data sharing in Amazon Redshift.

  • We recommend that you make your datashares publicly accessible. If you don't, subscribers on Amazon Web Services Data Exchange with publicly accessible consumer clusters won't be able to use your datashare.

  • We recommend that you don't delete an Amazon Web Services Data Exchange datashare shared to other Amazon Web Services accounts using the DROP DATASHARE statement. If you do, the Amazon Web Services accounts that have access to the datashare will lose access. This action is irreversible. Performing this type of alteration can breach data product terms in Amazon Web Services Data Exchange. If you want to delete an Amazon Web Services Data Exchange datashare, see DROP DATASHARE usage notes.

  • For cross-Region data sharing, you can create Amazon Web Services Data Exchange datashares to share licensed data.

  • When consuming data from a different Region, the consumer pays the Cross-Region data transfer fee from the producer Region to the consumer Region.