Issue with Lake Formation permissions - Users can see referenced tables when granted access to views

[ElearG]

Describe the bug

I've encountered what appears to be a bug with Lake Formation permissions when working with views and their referenced tables. According to AWS documentation, the SELECT permission should only allow users to query a table but not view its schema or metadata, while DESCRIBE permission is needed for those capabilities.

This issue creates significant problems for our data governance model:

Users see many tables they shouldn't directly interact with
It becomes difficult to implement a true abstraction layer using views
It violates our least-privilege access model
Creates confusion among end users who see more resources than they should

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

When a user is granted only SELECT permission on tables referenced by a view:

The user should be able to query the view successfully
The user should NOT see the referenced tables in Athena's interface
The user should NOT be able to list the schema or view the structure of the referenced tables

Current Behavior

When a user is granted only SELECT permission on tables referenced by a view:

The user can query the view (as expected)
The user can see ALL referenced tables in Athena's interface
The user can list the schema and examine the structure of the referenced tables

This appears to be a bug in the permission model, as the DESCRIBE permission (which controls visibility of table metadata) is not being enforced correctly.

Reproduction Steps

Create a Lake Formation database with tables and views
Create a view that references one or more tables
Grant a user/role the following permissions:

SELECT and DESCRIBE on the view
Only SELECT (not DESCRIBE) on the referenced tables

Login as that user and access Athena
Observe that the user can see and explore all referenced tables in Athena

Possible Solution

No response

Additional Information/Context

I've verified this behavior across multiple accounts and roles. I've also confirmed that the IAM permissions are correct and that this appears to be specific to how Lake Formation permissions interact with Athena's interface.
Has anyone else experienced this issue or found a workaround? Are there any configuration settings I might be missing?

SDK version used

1.37

Environment details (OS name and version, etc.)

Python 3.9