Repository navigation
Telemetry: send credential via x-amicode-token header - #210
Merged
Merged
Conversation
The run-corpus ingest now sits behind CloudFront with OAC, which signs each origin request with SigV4 in the Authorization header — overwriting the app token that rode Authorization: Bearer, so the Lambda rejected valid callers with bad_token (401). Inject the token on the custom x-amicode-token header instead; the gate, token source, and every other OTLP env var are unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Client sends the telemetry credential in the
x-amicode-tokenheader (wasAuthorization: Bearer). Matches the ingest, which readsx-amicode-token(aws-infra #205). Token still from~/.amico/cloud.json; gate unchanged. 743 tests pass. Pairs with the aws-infra pin-URL pivot.