1 個回答
- 最新
- 最多得票
- 最多評論
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.
已回答 3 個月前
相關內容
- 已提問 1 年前
- AWS 官方已更新 1 年前
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