This product is currently in Tech Preview and is not available for General Availability (GA). It should not be used in production environments, as features and functionality may change before the final GA release.

Understanding the Architecture

Understand the Architecture to install the Python Iceberg Protector.

The architecture of the Iceberg Protector using Python is depicted in the following diagram:

  1. Python Client: Sends Protegrity encryption-related table properties that drive how columns should be protected.

  2. Modified Pyiceberg: Accepts the Protegrity encryption-related table properties from the Python Client.

  3. Modified PyArrow / DataBatch Protection Service: Receives data from Modified Pyiceberg and passes it to Application Protector C for protection.

  4. Application Protector C: The core protection component. It performs the encryption/decryption of column data and routes the results to the RPAgent and the Log Forwarder. It also writes the protected output directly to the Protegrity Encrypted Parquet File.

  5. RPAgent: Forwards protection-related communication from Application Protector C to the ESA.

  6. Log Forwarder: Forwards logs from Application Protector C to the ESA.

  7. ESA: The central service that receives both policy/agent communication (via RPAgent) and logs (via Log Forwarder).

  8. Protegrity Encrypted Parquet File: The physical storage output produced by Application Protector C, containing Protegrity-encrypted Parquet data.

Pylceberg Protector: Modified Pyiceberg, Modified PyArrow/DataBatch Protection Service, Application Protector C, RPAgent, and Log Forwarder together make up the Pylceberg Protector.

End-to-end flow: The Python Client sends Protegrity encryption-related table properties → Modified Pyiceberg accepts these properties → data flows through Modified PyArrow/DataBatch Protection Service → Application Protector C encrypts/decrypts the data → protected data is written to the Protegrity Encrypted Parquet File, while protection communication and logs are forwarded via RPAgent and Log Forwarder respectively to the ESA.

Last modified : October 06, 2026