To resolve this, you can either disable public accessibility for the consumer endpoint or make the datashare publicly accessible. It's generally recommended to avoid public accessibility unless necessary. Publicly accessibile setting: If the consumer endpoint is publicly accessible but the datashare is not, data sharing won't be possible. Redshift serverless is encrypted by default, so you need to ensure that your producer is also encrypted. If you're unable to see datashare objects when describing the datashare, it could be due to one of the following scenarios:Įncryption: Both the producer and consumer should be encrypted to enable data sharing. Sharing data between provisioned clusters and serverless namespaces in Amazon Redshift is indeed possible. I've also tried deleting and then recreating both the permissions and datashare list using the reverse command to create the data share. However, when I use the following command, the list of schemas and tables registered for data sharing are not retrieved.
When I run the SHOW DATASHARES command in the Serverless Redshift query console, I get a list of data shares created in the provisioned Redshift cluster. I created a data share in the provisioned Redshift cluster and entered the Namespace ID information of Serverless Redshift as the Consumer Namespace ID. Can provisioned Redshift clusters and Serverless Redshift clusters share data when they are in the same region and under the same account?
0 kommentar(er)
