Pulling a container image from "registry.connect.redhat.com" unexpectedly redirects to AWS S3

Solution Verified - Updated -


  • When pulling a container image from "registry.connect.redhat.com", this fails with the following error message:

    Failed to pull image "registry.connect.redhat.com/seldonio/seldon-core-operator-bundle@sha256:0a179578abb46e9a2ea827374cdf3787f1020892cc589073ab8962f5c7a57368": rpc error: code = Unknown desc = Error parsing image configuration: Get "https://rhc4tp-prod-z8cxf-image-registry-us-east-1-evenkyleffocxqvofrk.s3.dualstack.us-east-1.amazonaws.com/docker/registry/v2/blobs/sha256/95/95484b2371976b3a6485b06ba75ba2e1cdda038f137af1e6085cca390c75ab1f/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&[..]": net/http: TLS handshake timeout

    According to the following Solution, AWS S3 does not need to be allowed on the firewall: Applying IP address filtering to Red Hat Container Registries. Why are we seeing the error above?

  • Pulling a container image from "registry.connect.redhat.com" redirects to AWS S3, is this expected?


  • OpenShift Container Platform 4.6
  • Container Registry registry.connect.redhat.com

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content