Zero-ETL Integration from RDS to Redshift Stuck in "Creation" Status

If your Zero-ETL integration is stuck in the "creating" status for over 24 hours, this likely indicates an issue that needs to be addressed. Here are several things you should check:

1. Verify that your source RDS PostgreSQL database is running a supported version. Not all versions are compatible with Zero-ETL integrations.

2. Check that you've correctly configured the required database parameters for your PostgreSQL instance. Incorrect parameter settings can cause the integration creation to stall.

3. For your target Amazon Redshift cluster, ensure that:

• Case sensitivity is properly enabled
• You've added the authorized principal and integration source
• If using a provisioned cluster, it's properly encrypted

4. If you've recently modified parameters in your source DB cluster's parameter group, you may need to reboot the DB cluster for these changes to take effect.

5. Check if there are any network connectivity issues between your RDS instance and Redshift cluster.

For complex issues that can't be resolved through these troubleshooting steps, it's recommended to contact AWS Support with the following information:

• Integration ARN and current status
• Any error messages from integration describe operations
• Database and Amazon Redshift cluster configurations
• Timeline of when the issue started occurring

A 24-hour delay is not typical for Zero-ETL integration creation, so there's likely an underlying issue that needs to be addressed.
Sources
Troubleshooting Aurora zero-ETL integrations - Amazon Aurora
Troubleshooting zero-ETL integrations - Amazon Redshift
Troubleshooting Zero-ETL integration - Oracle Database@AWS