From f9729dd5c3156c102c05a2fa3d62be2563c3d3cb Mon Sep 17 00:00:00 2001 From: Andrew Talbot Date: Fri, 20 Sep 2024 21:39:16 +0000 Subject: [PATCH] backport of commit 2fc8e35ec355f59f7b8669f1a089c997245e2859 --- .../docs/platform/aws/lambda-extension.mdx | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/website/content/docs/platform/aws/lambda-extension.mdx b/website/content/docs/platform/aws/lambda-extension.mdx index e2ef7f40f7ce..61e9718de65b 100644 --- a/website/content/docs/platform/aws/lambda-extension.mdx +++ b/website/content/docs/platform/aws/lambda-extension.mdx @@ -243,12 +243,16 @@ request will be forwarded to Vault and the response returned and cached. Currently, the cache key is a hash of the request URL path, headers, body, and token. - - - The Vault Lambda Extension cache key includes headers from proxy requests. As - a result, distributed tracing headers like `traceparent` can lead to - individualized hashes that make repeated requests appear unique and cause cache - misses. + + + The Vault Lambda Extension cache key includes headers from proxy requests, but + excludes the standard distributed tracing headers `traceparent` and + `tracestate` because trace IDs are unique per request and would lead to unique + hashes for repeated requests. + + Some distributed tracing tools may add nonstandard tracing headers, which can + also lead to individualized hashes that make repeated requests unique and + cause cache misses.