1回答
- 新しい順
- 投票が多い順
- コメントが多い順
1
Based on what's described here, it seems there is no error in cloudwatch logs for crawler.
Can you please make sure that there are no access denied errors. Also see if the role attached to crawler has access to that s3 path and s3 bucket KMS key if SSE-KMS CMK is the bucket encryption. Can you create a new role with required permissions and attach it to crawler and see if behavior changes. Verify that there are no explicit deny policies at bucket or KMS key level.
Also, I'd see if there are any already existing tables, which related to this data(files) in same database, as in that case also, you may not see new tables created.
Comment here how it goes, happy to assist further.
Abhishek
関連するコンテンツ
- 質問済み 9ヶ月前
- AWS公式更新しました 1年前
- AWS公式更新しました 3年前
- AWS公式更新しました 7ヶ月前
- AWS公式更新しました 2年前