feat(bedrock): Add bearer token authentication support for AgentCore #16556
+104
−73
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.
Description
This PR adds support for Cognito bearer token authentication to AWS Bedrock AgentCore, enabling dual authentication modes (AWS SigV4 IAM credentials OR bearer tokens).
Changes
sign_request()to check forbearerTokeninoptional_paramsAuthorization: Bearer <token>header instead of AWS SigV4 signingverbose_logger.debug()statements for authentication method selectionAuthentication Modes
1. AWS SigV4 (IAM) - Default
2. Bearer Token (Cognito) - New
Custom Callback Example
For LiteLLM Proxy deployments, you can use a custom callback to map HTTP headers to AgentCore parameters:
Testing
Tested with:
Breaking Changes
None - this is a backward-compatible addition. Existing AgentCore integrations continue to work with SigV4 authentication by default.