1 Answer
- Newest
- Most votes
- Most comments
1
There appears to be a problem with the IAM role in Lake Formation.
Make sure you have the necessary permissions as described in the following document.
https://docs.aws.amazon.com/lake-formation/latest/dg/service-linked-roles.html
Relevant content
- Accepted Answerasked 3 months ago
- asked 4 months ago
- asked a month ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
The issue was that, the when the lake formation has created the datalake location, the role was not assigned to AWSServiceRoleForLakeFormationDataAccess