How Red Hat Satellite communicates with Red Hat Content Delivery Network when synchronizing repositories
Contents
Overview
Applicable Environments
- Red Hat Satellite
Introduction
The purpose of this knowledge article is to provide an overview of the type of network traffic generated by Red Hat Satellite during content synchronization with the Red Hat Content Delivery Network (CDN). It is intended solely as a reference to help administrators understand which data flows between Red Hat Satellite and the Red Hat CDN during a content sync operation. This article does not cover performance considerations, security recommendations, or configuration guidance beyond describing the expected communication patterns.
How it Works
When a content sync triggers, the following data is transmitted outbound to cdn.redhat.com via port 443 (HTTPS):
- mTLS Authentication (Entitlement Certificates): Red Hat Satellite authenticates to the CDN using the certificates contained in your imported Subscription Manifest. This certificate transmits your Red Hat Account Number, Subscription identifiers, and Product SKUs to authorize the download.
- HTTP GET/HEAD Requests: Standard web requests targeting specific repository metadata (e.g.,
repomd.xml) and content chunks (RPMs, ISOs). - User-Agent String: A standard HTTP header identifying the client as the Pulp content manager.
For more KB articles/solutions related to Red Hat Satellite 6.x Repository Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Repository Issues.