Glue Table is recognized as unmanaged data asset
For demonstration purposes I have created two projects in Amazon DataZone. I added a CSV to an S3 bucket and crawled it into the pub Glue DB of that environment. Then I registered it into the catalog in DataZone. So far so good.
Now I am trying to subscribe to it in the second project and query the data with Athena. But when I click "Subscribe" the following message appears:
This is an unmanaged asset: DataZone will not be able to add this asset to any environments. You can reach out to the data owner(s) to find alternate ways to query this asset once approved.
Even though in the picture it's clearly visible that the data asset is a Glue table.
According to the documentation (https://docs.aws.amazon.com/datazone/latest/userguide/grant-access-to-unmanaged-asset.html) it should be possible to managed access to Glue tables automatically:
For some of these assets, Amazon DataZone can can automatically manage access grants. These assets are called managed assets and include Lake Formation-managed AWS Glue Data Catalog tables and Amazon Redshift tables and views.
- Topics
- Analytics
- Language
- English
asked 3 years ago1.6K views
- Newest
- Most votes
- Most comments
Notice the condition specified that Glue tables need to meet to use this feature:
"include Lake Formation-managed AWS Glue Data Catalog tables and Amazon Redshift tables and views"
Is yours in one of those cases?
Hello,
This error indicates that the AWS Lake Formation permissions are not enforced on the asset that you want to publish. This can happen in the following cases.
The Amazon S3 location of the asset is not registered in AWS Lake Formation. To fix the issue, log into your AWS Lake Formation console in the account where the table exists and register the Amazon S3 location either in AWS Lake Formation mode or Hybrid mode.
answered 2 years ago
Relevant content
asked 3 years ago
asked a year ago
Hi! Thank you for your quick response. I figured out that the CSV file was only in the right bucket but not at the Data Lake location. I re-added the file at that location and then it worked. This was not really clear by reading the documentation. Thanks!
For me, Glue tables are working post including the corresponding s3 location into Lake formation as managed Location. But for Glue catalog Views , so far publishing in DataZone is still throwing the exception: "Unmanaged asset Subscribers to this asset won’t be able to add it to environments or query it. Fix below issues to make this asset managed by Amazon DataZone. Unable to assume the Data Access Role. Please reach out to your admin to resolve the issue."
Any idea what is to be done for Glue Catalog Views?