DMS: Querying for 'public'.'person':'created_at' failed

The error message "Querying for 'public'.'person':'created_at' failed" suggests that the Data Migration Service (DMS) is encountering an issue when trying to query the created_at column from the person table in the public schema of your PostgreSQL database. Here are a few things you can check to troubleshoot this issue:

1. Check the Database Connection: Ensure that the DMS instance is correctly configured to connect to the PostgreSQL database. Verify the database host, port, user credentials, and any other connection-related settings.

2. Verify the Table and Column Existence: Confirm that the person table and the created_at column exist in the public schema of your PostgreSQL database. You can do this by directly connecting to the database and running a simple SELECT query on the table.

3. Examine the Database Permissions: Ensure that the user account used by the DMS instance has the necessary permissions to access the person table and the created_at column. Check the database user's permissions and grant any missing permissions if required.

4. Inspect the DMS Task Configuration: Review the DMS task configuration, especially the source database connection details and the table/column mapping. Ensure that the source table and column names are correctly specified.

5. Check for Schema Changes: If the database schema has been recently modified, the DMS task may not have been updated accordingly. Try updating the DMS task to reflect any changes made to the database structure.

6. Increase Logging Verbosity: You can try increasing the logging verbosity of the DMS instance to get more detailed information about the error. This may provide additional clues about the root cause of the issue.

7. Validate the Replication Process: Perform a test replication of a different table or a subset of the data to ensure that the DMS instance is functioning correctly. This can help isolate the issue to a specific table or column.

If you've checked all of these and the issue persists, you may need to reach out to AWS Support for further assistance. They can help you investigate the problem in more detail and provide guidance on how to resolve the "Querying for 'public'.'person':'created_at' failed" error. (edited)