feat(agentgateway-bootstrap): wire up Bedrock IRSA auth via pod-identity webhook - #304
Merged
Andy Lo-A-Foe (loafoe) merged 1 commit intoJul 23, 2026
Conversation
…ity webhook Defaults bedrock.auth.type to "irsa" (was "secret") and adds bedrock.auth.roleArn. When set, gateway-parameters.yaml annotates the dynamically-provisioned dataplane's ServiceAccount with eks.amazonaws.com/role-arn - the cluster's amazon-eks-pod-identity-webhook then injects AWS_ROLE_ARN/AWS_WEB_IDENTITY_TOKEN_FILE into the dataplane pod automatically, and agentgateway's Rust dataplane (which is what actually signs Bedrock requests, not the Go controller) picks these up via the standard AWS SDK credential chain with no further chart-side wiring - no AssumeRole config needed in AgentgatewayBackend at all, since implicit/ambient auth is exactly the webhook-injected credentials. Same pattern already proven working for hermes-agent and picoclaw on this cluster. The IAM role itself (trust policy + Bedrock permissions) is provisioned externally - this chart only takes the ARN, never creates it. roleArn defaults to empty, in which case the ServiceAccount renders identically to before this change (no annotation) - existing deployments using auth.type: secret, or a fresh irsa deploy before the IAM role exists yet, are unaffected.
Andy Lo-A-Foe (loafoe)
deleted the
feat/agentgateway-bootstrap-bedrock-irsa
branch
July 23, 2026 11:46
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
1 participant
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.
Summary
Defaults
bedrock.auth.typetoirsaand addsbedrock.auth.roleArn. When set,annotates the dynamically-provisioned dataplane's ServiceAccount with
eks.amazonaws.com/role-arn- the cluster'samazon-eks-pod-identity-webhooktheninjects the AWS STS web-identity env vars into the pod automatically, and agentgateway's
Rust dataplane (which signs Bedrock requests) picks these up via the standard AWS SDK
credential chain with zero further wiring. No
AssumeRoleconfig needed inAgentgatewayBackend- ambient/implicit auth is exactly the webhook-injectedcredentials.
Same pattern already used by
hermes-agent/picoclawon this cluster. The IAM role(trust policy + permissions) is provisioned externally; this chart only consumes the
ARN.
Test plan