1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi Gustavo,
The error message suggests that the script is trying to access a DynamoDB table that doesn’t exist. Double-check if the table exist and the table name matches in your script. Also, you may be using the region or access key you were using in the sandbox account for the dev account. So, verify that you used the correct AWS region and access key.
I hope it helps.
répondu il y a 3 mois
Contenus pertinents
- demandé il y a 7 mois
- demandé il y a un an
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a un an
SOLUTION: The table was there in both environments. Did more testing and isolated the issue. Found out that when catalog tables are prefixed from the crawler this will fail. Not sure about other data sources/sinks but this is true for DynamoDB catalog table as a sink