Hello! I solved Docker's pull rate limit 429 error by using an ECR pull through cache as specified here , I can confirm it works. However I'm facing the following error when I pull Redshift through my ECR endpoint:

Failure in destination: You must upgrade your platform version to use this connector version. Either downgrade your connector or upgrade platform to 0.63.7

I wasn't getting this error when pulling directly from Docker Hub using exactly the same Redshift version (3.5.3).

This error is triggered when a connector version that requires platform

0.63.7

(or higher) is used on an older Airbyte platform. The Redshift destination changelog explicitly warns about this for version

3.3.0

and above: > “Support for refreshes and resumable full refresh. **WARNING: You must upgrade to platform 0.63.7 before upgrading to this connector version.**” [[Redshift changelog](https://docs.airbyte.com/integrations/destinations/redshift#changelog)] So: - Redshift

3.5.3

is in the range of versions that assume platform

>= 0.63.7

. [[Redshift changelog](https://docs.airbyte.com/integrations/destinations/redshift#changelog)] - When you pulled from Docker Hub, the built‑in connector definition in Airbyte likely pointed to a version compatible with your current platform. - When you switched to your own ECR image, you effectively created a custom connector definition that bypasses the platform’s compatibility checks, so the runtime now sees a connector that requires a newer platform and throws the error (similar to what happens in the Postgres/ECR and BigQuery issues). [[Postgres ECR issue](https://github.com/airbytehq/airbyte/issues/54691); [BigQuery platform error](https://github.com/airbytehq/airbyte/issues/59702)] Based on the available information, the supported options are: 1. Upgrade your Airbyte platform to ≥

0.63.7

so it is compatible with Redshift

3.5.3

. 2. **Use an older Redshift destination version that does not require `0.63.7`** (a version prior to

3.3.0

) in your ECR mirror, and point your custom destination definition to that tag. The knowledge sources do not provide a more granular compatibility matrix or a workaround beyond “downgrade the connector or upgrade the platform,” so I can’t suggest anything more specific than those two paths.

Forgot to add that I'm using Airbyte 2.0.0 self-hosted on an AWS EKS cluster.