pg.ddx.io  pgbackrest/pgbackrest GitHub issues and pull requests  
help / color / mirror / Atom feed
[pgbackrest/pgbackrest] PR #2896: Support encryption context for S3 server-side encryption using KMS.
22+ messages / 4 participants
[nested] [flat]

* [pgbackrest/pgbackrest] PR #2896: Support encryption context for S3 server-side encryption using KMS.
@ 2026-11-03 19:02  "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
  0 siblings, 0 replies; 22+ messages in thread

From: qinruyao (@qinruyao) @ 2026-11-03 19:02 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

KMS grants can require an encryption context in addition to a key ID. Add `repo-s3-kms-encryption-context` so S3 repository writes can supply that context.

The optional hash uses repeated `key=value` entries, like `repo-storage-tag`, and requires `repo-s3-kms-key-id`. The S3 driver serializes the entries as sorted JSON and Base64-encodes the result once when it creates the storage object. It sends `x-amz-server-side-encryption-context` with the existing KMS headers on `PutObject` and `CreateMultipartUpload`.

When the option is unset, requests retain their existing behavior. Reads and upload parts do not send the context header. The documentation explains that context values are not secret.

```ini
repo1-s3-kms-key-id=bceb4f13-6939-4be3-910d-df54dee817b7
repo1-s3-kms-encryption-context=cluster_id=pg-prod-01
repo1-s3-kms-encryption-context=tenant_id=tenant-01
```

Local validation passed on Ubuntu 24.04, ARM64:

- Formatting and source lint.
- Unity build with warnings treated as errors.
- `storage/s3`, `config/parse`, `command/help`, and `doc/command/build/reference` tests with full coverage for the reported modules.
- Integration-test harness compilation.
- Command and configuration HTML generation with execution enabled, plus inspection of the option description, examples, and links.
- Inspection of the new option's help from the built binary.

The tests cover missing-key and malformed-entry errors, plus sorted JSON with escaped characters and UTF-8. They check signed upload headers and omission on reads and upload parts. They also retain KMS-without-context and non-KMS write coverage.

Integration workloads, Valgrind, and live AWS KMS validation have not run locally. The full documentation set was rendered with `--no-exe`; the executable user-guide examples and Debian/RHEL documentation workflow have not run locally.


Fixes https://github.com/pgbackrest/pgbackrest/issues/2891.

inline patch 1: build/config.yaml, doc/xml/reference.xml, src/config/config.auto.h and 7 more (+200/-10 lines) download inline-1.patchdiff --git a/build/config.yaml b/build/config.yaml index e20b77be03..b086b65216 100644 --- a/build/config.yaml +++ b/build/config.yaml @@ -2433,6 +2433,13 @@ option: deprecate: repo-s3-key-secret: {} + repo-s3-kms-encryption-context: + inherit: repo-s3-bucket + type: hash + required: false + depend: + option: repo-s3-kms-key-id + repo-s3-kms-key-id: inherit: repo-s3-bucket required: false diff --git a/doc/xml/reference.xml b/doc/xml/reference.xml index 716f9fdef6..051de1b5a9 100644 --- a/doc/xml/reference.xml +++ b/doc/xml/reference.xml @@ -1060,6 +1060,23 @@ <example>AQoDYXdzEPT//////////wEXAMPLEtc764bNrC9SAPBSM22 ...</example> </config-key> + <config-key id="repo-s3-kms-encryption-context" name="S3 Repository KMS Encryption Context"> + <summary>S3 repository KMS encryption context.</summary> + + <text> + <p>This option adds an encryption context for S3 server-side encryption with AWS KMS. It requires <br-option>repo-s3-kms-key-id</br-option>.</p> + + <p>Each entry is a key/value pair, for example <setting>repo1-s3-kms-encryption-context=cluster_id=pg-prod-01</setting>. Multiple entries require a separate option for each entry.</p> + + <p><backrest/> sends the context when it creates objects, including multipart uploads. This option does not change existing objects. S3 stores the context with each object and uses it to decrypt the object.</p> + + <p>Encryption context is not secret and must not contain sensitive information.</p> + </text> + + <example>cluster_id=pg-prod-01</example> + <example>tenant_id=tenant-01</example> + </config-key> + <config-key id="repo-s3-kms-key-id" name="S3 Repository KMS Key ID"> <summary>S3 repository KMS key.</summary> diff --git a/src/config/config.auto.h b/src/config/config.auto.h index 07ea853524..c64d7a51c7 100644 --- a/src/config/config.auto.h +++ b/src/config/config.auto.h @@ -146,7 +146,7 @@ Option constants #define CFGOPT_VERBOSE "verbose" #define CFGOPT_VERSION "version" -#define CFG_OPTION_TOTAL 202 +#define CFG_OPTION_TOTAL 203 /*********************************************************************************************************************************** Option value constants @@ -624,6 +624,7 @@ typedef enum cfgOptRepoS3Key, cfgOptRepoS3KeySecret, cfgOptRepoS3KeyType, + cfgOptRepoS3KmsEncryptionContext, cfgOptRepoS3KmsKeyId, cfgOptRepoS3ProcessCmd, cfgOptRepoS3Region, diff --git a/src/config/parse.auto.c.inc b/src/config/parse.auto.c.inc index b736d687ad..04fc88f05b 100644 --- a/src/config/parse.auto.c.inc +++ b/src/config/parse.auto.c.inc @@ -8035,6 +8035,83 @@ static const ParseRuleOption parseRuleOption[CFG_OPTION_TOTAL] = ), // opt/repo-s3-key-type ), // opt/repo-s3-key-type // ----------------------------------------------------------------------------------------------------------------------------- + PARSE_RULE_OPTION // opt/repo-s3-kms-encryption-context + ( // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_NAME("repo-s3-kms-encryption-context"), // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_TYPE(Hash), // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_RESET(true), // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_REQUIRED(false), // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_SECTION(Global), // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_MULTI(true), // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_GROUP_ID(Repo), // opt/repo-s3-kms-encryption-context + // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND_ROLE_MAIN_VALID_LIST // opt/repo-s3-kms-encryption-context + ( // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Annotate) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(ArchiveGet) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(ArchivePush) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Backup) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Check) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Expire) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Info) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Manifest) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(RepoGet) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(RepoLs) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(RepoRm) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Restore) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(StanzaCreate) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(StanzaDelete) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(StanzaUpgrade) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Verify) // opt/repo-s3-kms-encryption-context + ), // opt/repo-s3-kms-encryption-context + // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND_ROLE_ASYNC_VALID_LIST // opt/repo-s3-kms-encryption-context + ( // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(ArchiveGet) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(ArchivePush) // opt/repo-s3-kms-encryption-context + ), // opt/repo-s3-kms-encryption-context + // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND_ROLE_LOCAL_VALID_LIST // opt/repo-s3-kms-encryption-context + ( // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(ArchiveGet) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(ArchivePush) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Backup) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Restore) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Verify) // opt/repo-s3-kms-encryption-context + ), // opt/repo-s3-kms-encryption-context + // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND_ROLE_REMOTE_VALID_LIST // opt/repo-s3-kms-encryption-context + ( // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Annotate) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(ArchiveGet) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(ArchivePush) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Backup) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Check) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Expire) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Info) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Manifest) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(RepoGet) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(RepoLs) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(RepoRm) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Restore) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(StanzaCreate) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(StanzaDelete) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(StanzaUpgrade) // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTION_COMMAND(Verify) // opt/repo-s3-kms-encryption-context + ), // opt/repo-s3-kms-encryption-context + // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTIONAL // opt/repo-s3-kms-encryption-context + ( // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTIONAL_GROUP // opt/repo-s3-kms-encryption-context + ( // opt/repo-s3-kms-encryption-context + PARSE_RULE_OPTIONAL_DEPEND // opt/repo-s3-kms-encryption-context + ( // opt/repo-s3-kms-encryption-context + PARSE_RULE_VAL_OPT(RepoS3KmsKeyId), // opt/repo-s3-kms-encryption-context + ), // opt/repo-s3-kms-encryption-context + ), // opt/repo-s3-kms-encryption-context + ), // opt/repo-s3-kms-encryption-context + ), // opt/repo-s3-kms-encryption-context + // ----------------------------------------------------------------------------------------------------------------------------- PARSE_RULE_OPTION // opt/repo-s3-kms-key-id ( // opt/repo-s3-kms-key-id PARSE_RULE_OPTION_NAME("repo-s3-kms-key-id"), // opt/repo-s3-kms-key-id @@ -12338,5 +12415,6 @@ static const uint8_t optionResolveOrder[] = cfgOptRepoHostPort, // opt-resolve-order cfgOptRepoS3Key, // opt-resolve-order cfgOptRepoS3KeySecret, // opt-resolve-order + cfgOptRepoS3KmsEncryptionContext, // opt-resolve-order cfgOptRepoSftpHostFingerprint, // opt-resolve-order }; diff --git a/src/storage/s3/helper.c b/src/storage/s3/helper.c index 54eedbe51d..fda75bebc4 100644 --- a/src/storage/s3/helper.c +++ b/src/storage/s3/helper.c @@ -117,7 +117,8 @@ storageS3Helper(const unsigned int repoIdx, const bool write, StoragePathExpress cfgOptionIdxStr(cfgOptRepoS3Region, repoIdx), cfgOptionIdxStr(cfgOptRepoS3Service, repoIdx), keyType, (StorageS3UriStyle)cfgOptionIdxSeq(cfgOptRepoS3UriStyle, repoIdx), cfgOptionIdxStrNull(cfgOptRepoS3Key, repoIdx), cfgOptionIdxStrNull(cfgOptRepoS3KeySecret, repoIdx), cfgOptionIdxStrNull(cfgOptRepoS3Token, repoIdx), - cfgOptionIdxStrNull(cfgOptRepoS3KmsKeyId, repoIdx), cfgOptionIdxStrNull(cfgOptRepoS3SseCustomerKey, repoIdx), role, + cfgOptionIdxStrNull(cfgOptRepoS3KmsKeyId, repoIdx), cfgOptionIdxKvNull(cfgOptRepoS3KmsEncryptionContext, repoIdx), + cfgOptionIdxStrNull(cfgOptRepoS3SseCustomerKey, repoIdx), role, tokenFile, credUrl, credCmd, cfgOptionIdxStrNull(cfgOptRepoS3StsHost, repoIdx), (size_t)cfgOptionIdxUInt64(cfgOptRepoStorageUploadChunkSize, repoIdx), cfgOptionIdxKvNull(cfgOptRepoStorageTag, repoIdx), host, port, ioTimeoutMs(), protocolType, diff --git a/src/storage/s3/storage.c b/src/storage/s3/storage.c index 039492b794..19ec83b198 100644 --- a/src/storage/s3/storage.c +++ b/src/storage/s3/storage.c @@ -35,6 +35,7 @@ STRING_STATIC(S3_HEADER_TOKEN_STR, "x-amz-secur STRING_STATIC(S3_HEADER_SRVSDENC_STR, "x-amz-server-side-encryption"); STRING_STATIC(S3_HEADER_SRVSDENC_KMS_STR, "aws:kms"); STRING_STATIC(S3_HEADER_SRVSDENC_KMSKEYID_STR, "x-amz-server-side-encryption-aws-kms-key-id"); +STRING_STATIC(S3_HEADER_SRVSDENC_CONTEXT_STR, "x-amz-server-side-encryption-context"); STRING_STATIC(S3_HEADER_SSECUSTKEY_ALGO_STR, "x-amz-server-side-encryption-customer-algorithm"); STRING_STATIC(S3_HEADER_SSECUSTKEY_AES256_STR, "AES256"); STRING_STATIC(S3_HEADER_SSECUSTKEY_KEY_STR, "x-amz-server-side-encryption-customer-key"); @@ -110,6 +111,7 @@ struct StorageS3 String *secretAccessKey; // Secret access key String *securityToken; // Security token, if any const String *kmsKeyId; // Server-side encryption key + const String *kmsEncryptionContext; // Base64 JSON of the KMS encryption context const String *sseCustomerKey; // Base64 of SSE-C encryption key const String *sseCustomerKeyMd5; // Base64 of MD5 of SSE-C key size_t partSize; // Part size for multi-part upload @@ -598,6 +600,9 @@ storageS3RequestAsync(StorageS3 *const this, const String *const verb, const Str { httpHeaderPut(requestHeader, S3_HEADER_SRVSDENC_STR, S3_HEADER_SRVSDENC_KMS_STR); httpHeaderPut(requestHeader, S3_HEADER_SRVSDENC_KMSKEYID_STR, this->kmsKeyId); + + if (this->kmsEncryptionContext != NULL) + httpHeaderPut(requestHeader, S3_HEADER_SRVSDENC_CONTEXT_STR, this->kmsEncryptionContext); } // Set SSE-C headers when requested @@ -1327,7 +1332,8 @@ storageS3New( const String *const bucket, const String *const endPoint, const String *const region, const String *const service, const StorageS3KeyType keyType, const StorageS3UriStyle uriStyle, const String *const accessKey, const String *const secretAccessKey, const String *const securityToken, const String *const kmsKeyId, - const String *sseCustomerKey, const String *const credRole, const String *const tokenFile, const String *const credUrl, + const KeyValue *const kmsEncryptionContext, const String *sseCustomerKey, const String *const credRole, + const String *const tokenFile, const String *const credUrl, const StringList *const credCmd, const String *const stsHost, const size_t partSize, const KeyValue *const tag, const String *host, const unsigned int port, const TimeMSec timeout, const HttpProtocolType protocolType, const bool verifyPeer, const String *const caFile, const String *const caPath, const bool requesterPays, @@ -1349,6 +1355,7 @@ storageS3New( FUNCTION_TEST_PARAM(STRING, secretAccessKey); FUNCTION_TEST_PARAM(STRING, securityToken); FUNCTION_TEST_PARAM(STRING, kmsKeyId); + FUNCTION_LOG_PARAM(KEY_VALUE, kmsEncryptionContext); FUNCTION_TEST_PARAM(STRING, sseCustomerKey); FUNCTION_TEST_PARAM(STRING, credRole); FUNCTION_TEST_PARAM(STRING, tokenFile); @@ -1397,6 +1404,21 @@ storageS3New( .signingKeyDate = YYYYMMDD_STR, }; + if (kmsEncryptionContext != NULL) + { + MEM_CONTEXT_TEMP_BEGIN() + { + const String *const context = jsonFromVar(varNewKv(kvDup(kmsEncryptionContext))); + + MEM_CONTEXT_PRIOR_BEGIN() + { + this->kmsEncryptionContext = strNewEncode(encodingBase64, BUFSTR(context)); + } + MEM_CONTEXT_PRIOR_END(); + } + MEM_CONTEXT_TEMP_END(); + } + // Set prefetch and read over this->interface.prefetch = prefetch; this->interface.readOver = readOver; diff --git a/src/storage/s3/storage.h b/src/storage/s3/storage.h index 6b251b0fb5..d11b008d73 100644 --- a/src/storage/s3/storage.h +++ b/src/storage/s3/storage.h @@ -40,9 +40,9 @@ FN_EXTERN Storage *storageS3New( const String *path, bool write, time_t targetTime, StoragePathExpressionCallback pathExpressionFunction, const String *bucket, const String *endPoint, const String *region, const String *service, StorageS3KeyType keyType, StorageS3UriStyle uriStyle, const String *accessKey, const String *secretAccessKey, const String *securityToken, const String *kmsKeyId, - const String *sseCustomerKey, const String *credRole, const String *tokenFile, const String *credUrl, - const StringList *credCmd, const String *stsHost, size_t partSize, const KeyValue *tag, const String *host, - unsigned int port, TimeMSec timeout, HttpProtocolType protocolType, bool verifyPeer, const String *caFile, + const KeyValue *kmsEncryptionContext, const String *sseCustomerKey, const String *credRole, const String *tokenFile, + const String *credUrl, const StringList *credCmd, const String *stsHost, size_t partSize, const KeyValue *tag, + const String *host, unsigned int port, TimeMSec timeout, HttpProtocolType protocolType, bool verifyPeer, const String *caFile, const String *caPath, bool requesterPays, unsigned int prefetch, uint64_t readOver); #endif diff --git a/test/src/harness/host.c b/test/src/harness/host.c index 6492c946d8..f84866efaf 100644 --- a/test/src/harness/host.c +++ b/test/src/harness/host.c @@ -789,7 +789,7 @@ hrnHostConfig(HrnHost *const this) hrnHostRepo1Path(this), true, 0, NULL, STRDEF(HRN_HOST_S3_BUCKET), STRDEF(HRN_HOST_S3_ENDPOINT), STR(HRN_HOST_S3_REGION), STRDEF("s3"), storageS3KeyTypeShared, storageS3UriStyleHost, STRDEF(HRN_HOST_S3_ACCESS_KEY), STRDEF(HRN_HOST_S3_ACCESS_SECRET_KEY), NULL, NULL, NULL, NULL, NULL, - NULL, NULL, NULL, 5 * 1024 * 1024, NULL, hrnHostIp(s3), 443, ioTimeoutMs(), httpProtocolTypeHttps, + NULL, NULL, NULL, NULL, 5 * 1024 * 1024, NULL, hrnHostIp(s3), 443, ioTimeoutMs(), httpProtocolTypeHttps, false, NULL, NULL, NULL, 2, 8192); } MEM_CONTEXT_OBJ_END(); diff --git a/test/src/module/command/helpTest.c b/test/src/module/command/helpTest.c index 205f2d1884..7ac678c226 100644 --- a/test/src/module/command/helpTest.c +++ b/test/src/module/command/helpTest.c @@ -340,6 +340,7 @@ testRun(void) " --repo-s3-key S3 repository access key\n" " --repo-s3-key-secret S3 repository secret access key\n" " --repo-s3-key-type S3 repository key type\n" + " --repo-s3-kms-encryption-context S3 repository KMS encryption context\n" " --repo-s3-kms-key-id S3 repository KMS key\n" " --repo-s3-process-cmd S3 authentication process command\n" " --repo-s3-region S3 repository region\n" diff --git a/test/src/module/storage/s3Test.c b/test/src/module/storage/s3Test.c index 9cb8de6d0a..5e23aa763f 100644 --- a/test/src/module/storage/s3Test.c +++ b/test/src/module/storage/s3Test.c @@ -17,6 +17,8 @@ Test S3 Storage Constants ***********************************************************************************************************************************/ #define S3_TEST_HOST "s3.amazonaws.com" +#define S3_TEST_KMS_CONTEXT \ + "eyJjbHVzdGVyX2lkIjoicGctcHJvZC0wMSIsInRlbmFudF9pZCI6InRlbmFudC0wMSJ9" /*********************************************************************************************************************************** Calculate splitMax. This defines the point at which the maximum chunk size must be used in order to be able to upload the maximum @@ -78,6 +80,7 @@ typedef struct TestRequestParam const char *authorization; const char *range; const char *kms; + const char *kmsContext; const char *sseC; const char *ttl; const char *token; @@ -136,6 +139,9 @@ testRequest(IoWrite *write, Storage *s3, const char *verb, const char *path, Tes if (param.kms != NULL) strCatZ(request, ";x-amz-server-side-encryption;x-amz-server-side-encryption-aws-kms-key-id"); + if (param.kmsContext != NULL) + strCatZ(request, ";x-amz-server-side-encryption-context"); + if (param.sseC != NULL) { strCatZ( @@ -206,6 +212,9 @@ testRequest(IoWrite *write, Storage *s3, const char *verb, const char *path, Tes strCatFmt(request, "x-amz-server-side-encryption-aws-kms-key-id:%s\r\n", param.kms); } + if (param.kmsContext != NULL) + strCatFmt(request, "x-amz-server-side-encryption-context:%s\r\n", param.kmsContext); + // Add sseC key if (param.sseC != NULL) { @@ -371,6 +380,7 @@ testRun(void) TEST_RESULT_STR(driver->accessKey, accessKey, "check access key"); TEST_RESULT_STR(driver->secretAccessKey, secretAccessKey, "check secret access key"); TEST_RESULT_STR(driver->securityToken, NULL, "check security token"); + TEST_RESULT_STR(driver->kmsEncryptionContext, NULL, "check encryption context is unset"); TEST_RESULT_VOID( FUNCTION_LOG_OBJECT_FORMAT(driver->httpClient, httpClientToLog, logBuf, sizeof(logBuf)), "httpClientToLog"); @@ -527,6 +537,40 @@ testRun(void) driver = (StorageS3 *)storageDriver(storageRepoGet(0, false)); TEST_RESULT_STR_Z(driver->signingService, "s3", "check signing service is s3 for default repo-s3-service"); + + // ------------------------------------------------------------------------------------------------------------------------- + TEST_TITLE("KMS encryption context requires a key"); + + argList = strLstDup(commonArgList); + hrnCfgArgRawZ(argList, cfgOptRepoS3KmsEncryptionContext, "cluster_id=pg-prod-01"); + TEST_ERROR( + HRN_CFG_LOAD(cfgCmdArchivePush, argList), OptionInvalidError, + "option 'repo1-s3-kms-encryption-context' not valid without option 'repo1-s3-kms-key-id'"); + + // ------------------------------------------------------------------------------------------------------------------------- + TEST_TITLE("KMS encryption context requires key/value pairs"); + + argList = strLstDup(commonArgList); + hrnCfgArgRawZ(argList, cfgOptRepoS3KmsKeyId, "kmskey1"); + hrnCfgArgRawZ(argList, cfgOptRepoS3KmsEncryptionContext, "invalid"); + TEST_ERROR( + HRN_CFG_LOAD(cfgCmdArchivePush, argList), OptionInvalidError, + "key/value 'invalid' not valid for 'repo1-s3-kms-encryption-context' option"); + + // ------------------------------------------------------------------------------------------------------------------------- + TEST_TITLE("KMS encryption context sorts keys and escapes JSON"); + + argList = strLstDup(commonArgList); + hrnCfgArgRawZ(argList, cfgOptRepoS3KmsKeyId, "kmskey1"); + hrnCfgArgRawZ(argList, cfgOptRepoS3KmsEncryptionContext, "tenant_id=tenant\"\\\xc3\xa9"); + hrnCfgArgRawZ(argList, cfgOptRepoS3KmsEncryptionContext, "cluster_id=pg-prod-01"); + HRN_CFG_LOAD(cfgCmdArchivePush, argList); + + driver = (StorageS3 *)storageDriver(storageRepoGet(0, false)); + + TEST_RESULT_STR_Z( + strNewBuf(bufNewDecode(encodingBase64, driver->kmsEncryptionContext)), + "{\"cluster_id\":\"pg-prod-01\",\"tenant_id\":\"tenant\\\"\\\\\xc3\xa9\"}", "check encryption context JSON"); } // ***************************************************************************************************************************** @@ -778,6 +822,8 @@ testRun(void) hrnCfgArgRaw(argList, cfgOptRepoS3Role, credRole); hrnCfgArgRawZ(argList, cfgOptRepoS3KeyType, "auto"); hrnCfgArgRawZ(argList, cfgOptRepoS3KmsKeyId, "kmskey1"); + hrnCfgArgRawZ(argList, cfgOptRepoS3KmsEncryptionContext, "tenant_id=tenant-01"); + hrnCfgArgRawZ(argList, cfgOptRepoS3KmsEncryptionContext, "cluster_id=pg-prod-01"); hrnCfgEnvRawZ(cfgOptRepoS3SseCustomerKey, "rA1P"); hrnCfgArgRawZ(argList, cfgOptRepoStorageTag, "Key1=Value1"); hrnCfgArgRawZ(argList, cfgOptRepoStorageTag, " Key 2= Value 2"); @@ -1004,7 +1050,8 @@ testRun(void) testRequestP( service, s3, HTTP_VERB_PUT, "/file.txt", .content = "ABCD", .accessKey = "xx", .securityToken = "zz", - .kms = "kmskey1", .sseC = "rA1P", .tag = "%20Key%202=%20Value%202&Key1=Value1"); + .kms = "kmskey1", .kmsContext = S3_TEST_KMS_CONTEXT, .sseC = "rA1P", + .tag = "%20Key%202=%20Value%202&Key1=Value1"); testResponseP(service); // Make a copy of the signing key to verify that it gets changed when the keys are updated @@ -1034,7 +1081,18 @@ testRun(void) TEST_RESULT_BOOL(bufEq(driver->signingKey, oldSigningKey), false, "signing key changed"); // ----------------------------------------------------------------------------------------------------------------- - TEST_TITLE("write zero-length file"); + TEST_TITLE("read with KMS encryption context configured"); + + testRequestP(service, s3, HTTP_VERB_GET, "/file.txt", .sseC = "rA1P"); + testResponseP(service, .content = "ABCD"); + + TEST_RESULT_STR_Z(strNewBuf(storageGetP(storageNewReadP(s3, STRDEF("file.txt")))), "ABCD", "read file"); + + // ----------------------------------------------------------------------------------------------------------------- + TEST_TITLE("write zero-length file with KMS but without encryption context"); + + const String *const kmsEncryptionContext = driver->kmsEncryptionContext; + driver->kmsEncryptionContext = NULL; testRequestP( service, s3, HTTP_VERB_PUT, "/file.txt", .content = "", .kms = "kmskey1", .sseC = "rA1P", @@ -1047,8 +1105,11 @@ testRun(void) // ----------------------------------------------------------------------------------------------------------------- TEST_TITLE("write file in chunks with nothing left over on close"); + driver->kmsEncryptionContext = kmsEncryptionContext; + testRequestP( - service, s3, HTTP_VERB_POST, "/file.txt?uploads=", .kms = "kmskey1", .sseC = "rA1P", + service, s3, HTTP_VERB_POST, "/file.txt?uploads=", .kms = "kmskey1", .kmsContext = S3_TEST_KMS_CONTEXT, + .sseC = "rA1P", .tag = "%20Key%202=%20Value%202&Key1=Value1"); testResponseP( service, @@ -1090,6 +1151,8 @@ testRun(void) // ----------------------------------------------------------------------------------------------------------------- TEST_TITLE("error in success response of multipart upload"); + driver->kmsEncryptionContext = NULL; + // Stop writing tags driver->tag = NULL;
^ permalink raw [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-04 14:32  "hunleyd (@hunleyd)" <noreply+hunleyd@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: hunleyd (@hunleyd) @ 2026-11-04 14:32 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

(on src/storage/s3/storage.c:1420)

`this->kmsEncryptionContext = strNewEncode(encodingBase64, BUFSTR(jsonFromVar(varNewKv(kvDup(kmsEncryptionContext)))));` is the same as those 13 lines, no?

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896 (changes requested): Support encryption context for S3 server-side encryption using KMS.
@ 2026-11-04 14:33  "hunleyd (@hunleyd)" <noreply+hunleyd@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: hunleyd (@hunleyd) @ 2026-11-04 14:33 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>



^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-04 19:17  "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: qinruyao (@qinruyao) @ 2026-11-04 19:17 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

(on src/storage/s3/storage.c:1411)

The memory-context macros freed the intermediate objects immediately. Since this runs once per storage instance, I’ve removed them to simplify the code in the new PR iteration.

I kept the two statements because BUFSTR expands its argument three times. Inlining the conversion would repeat the map copy and JSON serialization three times. Using a local variable evaluates that expression once:
```
const String *const context = jsonFromVar(varNewKv(kvDup(kmsEncryptionContext)));
this->kmsEncryptionContext = strNewEncode(encodingBase64, BUFSTR(context));
```

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896 (approved): Support encryption context for S3 server-side encryption using KMS.
@ 2026-11-05 14:05  "hunleyd (@hunleyd)" <noreply+hunleyd@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: hunleyd (@hunleyd) @ 2026-11-05 14:05 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>



^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-05 18:23  "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: qinruyao (@qinruyao) @ 2026-11-05 18:23 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

hi @hunleyd, 
thanks for the approval! Are you able to approve the pending workflow run?

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896 (approved): Support encryption context for S3 server-side encryption using KMS.
@ 2026-11-06 09:20  "pgstef (@pgstef)" <noreply+pgstef@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: pgstef (@pgstef) @ 2026-11-06 09:20 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

The PR looks good to me too, and the CI workflow passed successfully 👍

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-06 11:39  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: dwsteele (@dwsteele) @ 2026-11-06 11:39 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@dwsteele assigned @dwsteele.

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-06 11:40  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: dwsteele (@dwsteele) @ 2026-11-06 11:40 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@dwsteele applied label "enhancement".

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-06 11:40  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: dwsteele (@dwsteele) @ 2026-11-06 11:40 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@dwsteele applied label "module [core]".

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-06 11:40  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: dwsteele (@dwsteele) @ 2026-11-06 11:40 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@dwsteele set milestone to "2.61.0".

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-06 18:22  "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: qinruyao (@qinruyao) @ 2026-11-06 18:22 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@qinruyao closed this.

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-06 18:22  "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: qinruyao (@qinruyao) @ 2026-11-06 18:22 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@qinruyao reopened this.

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-06 18:25  "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: qinruyao (@qinruyao) @ 2026-11-06 18:25 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

Hi, @dwsteele I got 2 approvals, could you review and help merge the PR if looks good?

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-09 19:14  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: dwsteele (@dwsteele) @ 2026-11-09 19:14 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@qinruyao There are other PRs ahead of yours so please be patient (next feature release is January). I took a quick look and there are a number of minor issues to be resolved before this can be committed.

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option.
@ 2026-11-09 22:56  "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: qinruyao (@qinruyao) @ 2026-11-09 22:56 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

> @qinruyao There are other PRs ahead of yours so please be patient (next feature release is January). I took a quick look and there are a number of minor issues to be resolved before this can be committed.

Thanks @dwsteele for the context, I’ll wait for your review comments and address the issues you flag.

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896 (approved): Support encryption context for S3 server-side encryption using KMS.
@ 2026-11-17 14:45  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: dwsteele (@dwsteele) @ 2026-11-17 14:45 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

I made a few changes (see commit history). The important ones are:

- Rename the option.
- Include header only for writable storage.

Just checking -- you have tested this against real S3? Even if you have, would be good to do one final test before this gets committed.

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Support encryption context for S3 server-side encryption using KMS.
@ 2026-11-20 00:52  "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: qinruyao (@qinruyao) @ 2026-11-20 00:52 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

> I made a few changes (see commit history). The important ones are:
> 
> * Rename the option.
> * Include header only for writable storage.
> 
> Just checking -- you have tested this against real S3? Even if you have, would be good to do one final test before this gets committed.

@dwsteele Thanks so much for the careful review and updates! Yes, I've verified the new changes with expected test result - see the test cases and logs below. Let me know if you have any other questions.

**1. run patched pgbackrest with encryption context configured (after the KMS key creation and policy setup)**
    **Test result:** backup succeeded, and aws cloudtrail event (attached below) confirmed the correct encryption context were used.
    **2. run patched pgbackrest with the same key without s3-kms-context (and one wrong kms context entry) configured on the same cluster**
    **Test result:** backup failed access denied error which is expected
```
AccessDenied: no identity-based policy allows the kms:Decrypt action
backup command end: aborted with exception [039]
```

  **3. run not patched pgbackrest with the same key on a different cluster**
**Test result:** backup failed with AccessDenied error.
```
AccessDenied: User:
arn:aws:sts::083332610557:assumed-role/s3-operations/pgBackRest
is not authorized to perform: kms:GenerateDataKey
on resource:
arn:aws:kms::key/keyid, because no resource-based policy allows the kms:GenerateDataKey action
```

**redacted Aws cloudtrail event**
```

{
  "eventVersion": "1.11",
  "userIdentity": {
    "type": "AWSAccount",
    "principalId": ":pgBackRest",
    "accountId": "",
    "invokedBy": "fas.s3.amazonaws.com"
  },
  "eventSource": "kms.amazonaws.com",
  "eventName": "Decrypt",
  "awsRegion": "-2",
  "sourceIPAddress": ".s3.amazonaws.com",
  "userAgent": ".s3.amazonaws.com",
  "requestParameters": {
    "encryptionAlgorithm": "SYMMETRIC_DEFAULT",
    **"encryptionContext": {
      "tenant_id": "tenant-01",
      "cluster_id": "pg-prod-01",**
      "aws:s3:arn": "arn:aws:s3:::backups-bzt9/pgbackrest/postgres-operator/s3kmsctx-1119/repo2/backup/db/20261120-000445F/backup.manifest.copy"
    }
  },
  "responseElements": null,
  "additionalEventData": {
    "keyMaterialId": ""
  },
  "requestID": "ecb7b0fa-e0a7-4785-9822-f10a902f7737",
  "eventID": "cf39a620-b67b-39f0-81d3-3ce756d4fc79",
  "readOnly": true,
  "resources": [
    {
      "accountId": "",
      "type": "AWS::KMS::Key",
      "ARN": "arn:aws:kms:ap-southeast-2::key/07fe82be"
    }
  ],
  "eventType": "AwsApiCall",
  "managementEvent": true,
  "recipientAccountId": "",
  "sharedEventID": "9a4",
  "eventCategory": "Management"
}

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Support encryption context for S3 server-side encryption using KMS.
@ 2026-11-20 13:50  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: dwsteele (@dwsteele) @ 2026-11-20 13:50 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@dwsteele renamed this.

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Support encryption context for S3 server-side encryption using KMS.
@ 2026-11-20 13:55  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: dwsteele (@dwsteele) @ 2026-11-20 13:55 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@dwsteele merged this (commit 7548f7530c59).

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Support encryption context for S3 server-side encryption using KMS.
@ 2026-11-20 13:55  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: dwsteele (@dwsteele) @ 2026-11-20 13:55 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@dwsteele closed this.

^ permalink  raw  [nested|flat] 22+ messages in thread

* Re: [pgbackrest/pgbackrest] PR #2896: Support encryption context for S3 server-side encryption using KMS.
@ 2026-11-20 14:02  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  20 siblings, 0 replies; 22+ messages in thread

From: dwsteele (@dwsteele) @ 2026-11-20 14:02 UTC (permalink / raw)
  To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>

@qinruyao Excellent! Thank you for testing.

^ permalink  raw  [nested|flat] 22+ messages in thread


end of thread, other threads:[~2026-11-20 14:02 UTC | newest]

Thread overview: 22+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-11-03 19:02 [pgbackrest/pgbackrest] PR #2896: Support encryption context for S3 server-side encryption using KMS. "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
2026-11-04 14:32 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "hunleyd (@hunleyd)" <noreply+hunleyd@github.com>
2026-11-04 14:33 ` Re: [pgbackrest/pgbackrest] PR #2896 (changes requested): Support encryption context for S3 server-side encryption using KMS. "hunleyd (@hunleyd)" <noreply+hunleyd@github.com>
2026-11-04 19:17 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
2026-11-05 14:05 ` Re: [pgbackrest/pgbackrest] PR #2896 (approved): Support encryption context for S3 server-side encryption using KMS. "hunleyd (@hunleyd)" <noreply+hunleyd@github.com>
2026-11-05 18:23 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
2026-11-06 09:20 ` Re: [pgbackrest/pgbackrest] PR #2896 (approved): Support encryption context for S3 server-side encryption using KMS. "pgstef (@pgstef)" <noreply+pgstef@github.com>
2026-11-06 11:39 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-11-06 11:40 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-11-06 11:40 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-11-06 11:40 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-11-06 18:22 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
2026-11-06 18:22 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
2026-11-06 18:25 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
2026-11-09 19:14 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-11-09 22:56 ` Re: [pgbackrest/pgbackrest] PR #2896: Add S3 KMS encryption context option. "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
2026-11-17 14:45 ` Re: [pgbackrest/pgbackrest] PR #2896 (approved): Support encryption context for S3 server-side encryption using KMS. "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-11-20 00:52 ` "qinruyao (@qinruyao)" <noreply+qinruyao@github.com>
2026-11-20 13:50 ` "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-11-20 13:55 ` "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-11-20 13:55 ` "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-11-20 14:02 ` "dwsteele (@dwsteele)" <noreply+dwsteele@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