- Newest
- Most votes
- Most comments
This is indeed unexpected behavior from a user's perspective, but it is currently a known limitation of the AWS Management Console, specifically for Redshift Serverless. The "S3 event integrations" page in the Web UI was primarily designed to manage integrations for provisioned Redshift clusters and has not yet been fully updated to display the associated auto-copy jobs when the target is a Serverless namespace. Your observation is correct: while the underlying integration and the copy job are functioning perfectly, the console simply lacks the capability to list or manage these jobs for the Serverless environment.
The correct and officially supported way to monitor and manage your auto-copy jobs in Redshift Serverless is exactly as you've discovered: by using SQL commands directly within your namespace. The sys_copy_job view is the source of truth for viewing job status, configurations, and history. Similarly, any management tasks must be performed programmatically via SQL.
*For managing these jobs moving forward, you should rely on the following: * Viewing Jobs: Continue using
SELECT * FROM sys_copy_job;
to see all defined jobs and their status.
Monitoring Errors: Check SELECT * FROM stl_load_errors; or query the sys_load_error_detail view to diagnose any files that fail to copy.
Altering or Dropping Jobs: Use the SQL commands ALTER COPY JOB ... and DROP COPY JOB ... to make changes or remove a job.
In short, your setup is correct, and the jobs are not at risk. The discrepancy is purely a gap in the current UI functionality for Redshift Serverless, and for now, you must rely on SQL queries for all management and monitoring tasks related to the jobs themselves.
answered a year ago
Yes, this behavior is expected. While your auto-copy job is working correctly (as evidenced by data being loaded successfully and the job appearing in the sys_copy_job system table), there are some limitations with how auto-copy jobs appear in the Amazon Redshift web UI.
Currently, you can monitor and manage your auto-copy jobs primarily through SQL queries against system tables rather than through the web UI. To check the status and details of your auto-copy jobs, you can use the following system tables:
SYS_COPY_JOB- Shows basic information about your configured auto-copy jobsSYS_COPY_JOB_DETAIL- Provides details about the S3 files that have been loaded, are pending ingestion, or have encountered errorsSYS_COPY_JOB_INFO- Contains additional information about the copy jobsSTL_ERROR- Can help identify any errors that might be occurring
Auto-copy is available for both Amazon Redshift Serverless and Amazon Redshift RA3 Provisioned data warehouses, but the web UI integration for managing these jobs may not be fully implemented yet. For now, the recommended approach is to continue using SQL queries to monitor and manage your auto-copy jobs.
Sources
Redshift auto copy job is not working | AWS re:Post
Troubleshooting S3 event integration and COPY JOB errors - Amazon Redshift
COPY JOB - Amazon Redshift
Announcing general availability of auto-copy for Amazon Redshift - AWS
Relevant content
asked a year ago
asked a year ago
asked a year ago
asked 2 years ago

Thank you for the quick response! Hope AWS adds a mention about this in the integrations page.