added AWS SigV4 support for MCP Servers and Agents - #120
Merged
Conversation
GGabriele
approved these changes
Aug 11, 2026
GGabriele
approved these changes
Aug 11, 2026
mitchn82
approved these changes
Aug 11, 2026
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
4 participants
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.
Overview
Added AWS SigV4 upstream authentication support to Agents and MCP Servers, in both directions.
What it translates
AI Gateway config.upstream.auth (type: aws) ⇄ the auth record (provider: aws_iam + nested aws_iam options) on the ai-a2a-proxy / ai-mcp-proxy plugins. Also wired agent config.proxy → proxy_config (MCP already had it). Core work is a field-name renaming (access_key_id↔aws_access_key_id, region↔aws_region, type: aws↔provider: aws_iam).
New files: