1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi,
Maybe someone will know better than me but it might be worth checking that your include path is configured correctly and pointing to the right bucket if you haven't done so already?
From the doc here
*When evaluating what to include or exclude in a crawl, a crawler starts by evaluating the required include path. For Amazon S3, MongoDB, MongoDB Atlas, Amazon DocumentDB (with MongoDB compatibility), and relational data stores, you must specify an include path.
For Amazon S3 data stores, include path syntax is bucket-name/folder-name/file-name.ext. To crawl all objects in a bucket, you specify just the bucket name in the include path. The exclude pattern is relative to the include path*
répondu il y a 8 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a 6 mois
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 7 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
Hi James, thanks for the response!
I'm fairly certain my path is configured correctly or else none of my files would make it to the table. Also the crawler is able to see the files or else CloudWatch wouldn't claim that it is excluding them