2 Answers
- Newest
- Most votes
- Most comments
0
Eventually, I found out that I use incorrect writing method in this case
- Correct method: glueContext.write_dynamic_frame.from_catalog
- Incorrect method: glueContext.write_dynamic_frame.from_option
Quoted from docs
Writes a DynamicFrame using the specified catalog database and table name.
answered a year ago
0
Once you register a location to be managed by LakeFormation, you should not use s3 permissions to handle it since it.
Now any client API trying to access that table needs to be LakeFormation away in order to be able to use the delegated access permissions, for instance DynamicFrame is able write into such table but not if you write directly to s3 or you use DataFrame.
Relevant content
- asked 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 days ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 5 months ago
The amazon-reviews-pds bucket is data source which is a publicly available. My lake (destination bucket) permissions not written in the policy and grant permissions via Lake Formation.
Actually, if both IAM and Lake Formation grants permission, the the Glue Role is still able to write to S3, but it is not best practice.