liveBook · Manning

Server-side encryption

As explained in Architecting an Apache Iceberg Lakehouse

Server-side encryption is encryption performed by a storage service before data is persisted and decrypted when authorized data is accessed.

Server-side encryption shifts encryption-at-rest responsibilities to the object storage service, protecting persisted data without requiring client application changes. section 5.2.2

Its architectural role includes:

  • Using platform-managed encryption by default, with customer-managed keys or hardware security modules available on supported services. section 5.4.4
  • Supporting compliance through integration with IAM, access logging, audit services, and policy management. section 5.2.2 section 5.5.2
  • Requiring organizations to balance operational simplicity, key-control requirements, data residency, and existing identity infrastructure. section 5.5.2

Regulated cloud lakehouse

A financial institution can use Amazon S3 or Google Cloud Storage with customer-managed keys, object-level access logging, and CloudTrail or GCP Audit Logs to support auditable Iceberg data access. section 5.5.2

How Architecting an Apache Iceberg Lakehouse covers it

How deep it goes
Defines encryption at rest and identifies key-management and audit integrations, but does not detail cryptographic implementation.
Examples
Uses Amazon S3 and Google Cloud Storage scenarios involving customer-managed keys, access logging, and cloud audit services.
What you can do after
Operate object-storage encryption with managed keys and connect it to access-control and audit requirements.
How it connects
Connects object storage with IAM, customer-managed keys, audit logging, data residency, and Apache Iceberg.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting an Apache Iceberg Lakehouse. The section links point to the parts of the book it draws on.