- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Check the IAM role associated with the crawler. Most likely you don't have correct permission.
When you create the crawler, if you choose to create an IAM role(the default setting), then it will create a policy for S3 object you specified only. if later you edit the crawler and change the S3 path only. The role associated with the crawler won't have permission to the new S3 path.
Sometimes, deleting old role and edit the crawler to create new one would help too
I think it worked but now I have this error below but I talked with the admin of the aws services and he did the steps showed: nsufficient Lake Formation permission(s) on archivoscsv (Database name: aws-glue-lalo-test-crawler, Table Name: archivoscsv) (Service: AWSGlue; Status Code: 400; Error Code: AccessDeniedException; Request ID: 8cd54006-a723-4ea8-809a-9c70308f6fe4; Proxy: null). For more information, see Setting up IAM Permissions in the Developer Guide (http://docs.aws.amazon.com/glue/latest/dg/getting-started-access.html).
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
Where is not appearing, LF, Glue page, Athena, etc?, how does that relate with "changing AIM role permissions"?
Gonzalo I run the crawler but the table doesn't appear in tables and also not appearing in database
Gonzalo I run the crawler but the table doesn't appear in tables and also not appearing in database