huaxingao commented on code in PR #14621:
URL: https://github.com/apache/iceberg/pull/14621#discussion_r2553778010


##########
docs/docs/encryption.md:
##########
@@ -0,0 +1,112 @@
+---
+title: "Encryption"
+---
+<!--
+ - Licensed to the Apache Software Foundation (ASF) under one or more
+ - contributor license agreements.  See the NOTICE file distributed with
+ - this work for additional information regarding copyright ownership.
+ - The ASF licenses this file to You under the Apache License, Version 2.0
+ - (the "License"); you may not use this file except in compliance with
+ - the License.  You may obtain a copy of the License at
+ -
+ -   http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing, software
+ - distributed under the License is distributed on an "AS IS" BASIS,
+ - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ - See the License for the specific language governing permissions and
+ - limitations under the License.
+ -->
+
+# Encryption
+
+Iceberg table encryption protects confidentiality and integrity of table data 
in an untrusted storage. The `data`, `delete`, `manifest` and `manifest list` 
files are encrypted and tamper-proofed before being sent to the storage backend.
+
+The `metadata.json` file does not contain confidential information, and is 
therefore not encrypted.
+
+Currently, table encryption is supported with the Hive and REST catalogs.
+
+Two parameters are required to activate encryption of a table,
+1. Catalog property `encryption.kms-impl`, that specifies the class path for a 
client of a KMS ("key management service").
+2. Table property `encryption.key-id`, that specifies the ID of a master key 
used to encrypt and decrypt the table. Master keys are stored and managed in 
the KMS.
+

Review Comment:
   Could we add a brief ‘How it works’ subsection (per‑file AES key → AES‑GCM 
encrypt → wrapKey + store wrapped key → unwrapKey on read → decrypt



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to