1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
One possible reason could be Lake formation permissions that are needed for user for the database table level. Try the below steps and let me know if you still face any issues:
STEP 1: Table access
To grant access, please Go to "AWS Lake Formation" > "Data Lake permissions"
Choose the IAM users and roles from drop down
Choose Named data catalog resources
Choose Table(s) and provide "Select" & "Describe" access (or more as needed)
If it is not resolved, proceed to Step 2
STEP 2: Database access
To grant access, please Go to "AWS Lake Formation" > "Data Lake permissions"
Choose the IAM users and roles from drop down
Choose Named data catalog resources
Choose database (dont choose tables) and provide "Describe" access (or more as needed)
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
I'm having the exact same issue (Lake Formation managed Governed Table, generic user error, etc). Not only using the admin account with access to everything, but I specifically added the permissions as described on this answer, to no avail. Could there be something else that is causing this?