Please refer to this article https://docs.aws.amazon.com/lake-formation/latest/dg/access-control-fine-grained.html
The default method for backwards compatibility with AWS Glue is as follows:
“Open means that the special permission Super is granted to the group IAMAllowedPrincipals, where IAMAllowedPrincipals is automatically created and includes any IAM users and roles that are allowed access to your Data Catalog resources by your IAM policies, and the Super permission enables a principal to perform every supported Lake Formation operation on the database or table on which it is granted.” By default, Lake Formation permissions are made backwards compatible and transparent to those who do not want to use LF. Therefore, it works as if there is no LF. This was achieved by using the special IAM Group and the root user not being a part of that special group “IAM_ALLOWED_PRINCIPALS” created the error.
Hope this helps.
Using Athena to query AWS Lake Formation databaseasked 5 months ago
Access error : Spark query from AWS EMR with AWS Lake Formationasked 8 months ago
QuickSight DataSource created using boto3 is not able to access LakeFormation data through Athenaasked 2 months ago
Data Mesh on AWS Lake Formationasked a month ago
Lake Formation support for Delta Lakeasked 2 months ago
Athena query: Insufficient Lake Formation permission(s): Illegal permission combinationasked 8 months ago
Connecting Users to AWS Athena and AWS Lake Formation via Tableau Desktop using the Simba Athena JDBC Driver and Okta as Identity Providerasked 3 months ago
Is it possible to specify DB snapshot in AWS Lake Formation?Accepted Answerasked 2 years ago
Are you able to hide tables in a database using Lake Formation Taggingasked 6 months ago
lake formation on iceberg TablesAccepted Answerasked 25 days ago