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 21:34:48 +0000
Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2244-rc4591905734@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:890)
nit: "Writers of an encrypted column need no privileges on the metadata schema" reads as if it includes the application, but the plugin's connection is itself a writer and always needs `SELECT`. Could we separate the two reasons the tables are read?
On MySQL the trigger reads the metadata as its definer, so a role that writes an encrypted column without going through the plugin (for example, a batch job or the `mysql` client) needs no privileges on the metadata schema. The plugin still reads both tables itself, so the database user it connects as always needs the `SELECT` grants above.
While you're editing this paragraph, there's also a comma splice in "...which is the account that installed them, the shipped script sets no `SQL SECURITY` clause." Parentheses would fix it: "...which is the account that installed them (the shipped script sets no `SQL SECURITY` clause)."