By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Glue: An error occurred while calling o123.pyWriteDynamicFrame. Requested resource not found for DynamoDB data catalog table.

0

Error Category: RESOURCE_NOT_FOUND_ERROR; An error occurred while calling o123.pyWriteDynamicFrame. Requested resource not found: Table: datacatalog_table_name not found (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ResourceNotFoundException; Request ID: 5OGG96FFQ5NB78QNI50526CRJNVV4KQNSO5AEMVJF66Q9ASUAAJG; Proxy: null)

After working and getting my glue job to succeed in the sandbox account I am still not able to get it to connect in my dev account. In both accounts:

I have created identical dynamoDB tables I have crawled them I have performed the same glue jobs.

One works and one is giving me this error

Topics
DatabaseAnalytics
Tags
Aurora PostgreSQLAWS GlueAmazon DynamoDBAmazon AuroraExtract Transform & Load Data
Language
English
Gustavo
asked 7 months ago333 views
1 Answer
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.

profile pictureAWS
BezuW
answered 7 months ago
  • Gustavo
    7 months ago

    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

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content