pg.ddx.io  aws/aws-advanced-jdbc-wrapper GitHub issues and pull requests  
help / color / mirror / Atom feed
From: aaron-congo (@aaron-congo) <noreply+aaron-congo@github.com>
To: aws/aws-advanced-jdbc-wrapper <noreply+aws-aws-advanced-jdbc-wrapper@github.com>
Subject: Re: [aws/aws-advanced-jdbc-wrapper] PR #2244: docs: kms least privilege
Date: Mon, 16 Nov 2026 22:11:52 +0000
Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2244-rc4592327484@github.com> (raw)
In-Reply-To: <gh-aws-aws-advanced-jdbc-wrapper-2244@github.com>
References: <gh-aws-aws-advanced-jdbc-wrapper-2244@github.com>

(on docs/using-the-jdbc-driver/using-plugins/UsingTheKmsEncryptionPlugin.md:877)

The block above revokes from `PUBLIC` but grants `SELECT` back only to `app_runtime`. Any other role that writes an encrypted column and used to read the metadata through `PUBLIC` (an ETL or batch role, for example) then fails inside `validate_encrypted_data_hmac` with `permission denied for table key_storage`.

This paragraph mentions the requirement, but people tend to copy the SQL block as-is. A commented placeholder line in the block would make this harder to miss:

```sql
-- Repeat for every other role that writes an encrypted column
GRANT SELECT ON encrypt.key_storage, encrypt.encryption_metadata TO <other_writer_role>;
```


view thread (15+ messages)  latest in thread

Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2244-rc4592327484@github.com>
Permalink:  ../gh-aws-aws-advanced-jdbc-wrapper-2244-rc4592327484@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox