[GH-ISSUE #1961] Cloud KMS support #235

New issue

Open

opened 2026-03-03 12:09:20 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 12:09:20 +03:00

Owner

Originally created by @kaiju on GitHub (May 8, 2025).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/1961

GCS supports encrypting objects with customer-managed encryption keys in Cloud KMS instead of the default bucket key: https://cloud.google.com/storage/docs/encryption/customer-managed-keys

As far as I can tell, fake-gcs-server is fine with receiving upload requests with the kmsKeyName parameter, but doesn't return a kmsKeyName property on the resulting object resource.

I make heavy use of this functionality and I'd like to be able to use this fake-gcs-server in my tests.

If there's no existing plans to implement this, I'd be happy to take a stab at it.

Originally created by @kaiju on GitHub (May 8, 2025). Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/1961 GCS supports encrypting objects with customer-managed encryption keys in Cloud KMS instead of the default bucket key: https://cloud.google.com/storage/docs/encryption/customer-managed-keys As far as I can tell, fake-gcs-server is fine with receiving upload requests with the `kmsKeyName` parameter, but doesn't return a `kmsKeyName` property on the resulting object resource. I make heavy use of this functionality and I'd like to be able to use this fake-gcs-server in my tests. If there's no existing plans to implement this, I'd be happy to take a stab at it.