aws / aws/bedrock-agentcore-sdk-python
Support passing workload identity name to `require_access_token`
- Dominant language
- Python
- Stars
- 761
- Forks
- 147
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 7
Description
**Is your feature request related to a problem? Please describe.**
I want to use the 3LO flow with Identity outside of Runtime. As of now, this SDK falls back to the local auth settings expecting the `".agentcore.json"` which is not set by us. Hence, the SDK falls back to creating an Identity Workload but the agent's execution roles correctly gets an exception denied.
**Describe the solution you'd like**
I would like to use the decorator and pass the workload identity name. I would expect the decorator to get the workload access token and continue as is.
**Describe alternatives you've considered**
- Placing the `".agentcore.json"`
- Setting the `BedrockAgentCoreContext`
**Additional context**
Agent runs on Amazon ECS
Contributor guide
Research direction
Start by locating the Python implementation of `require_access_token` and the decorator's handling of `.agentcore.json` and `BedrockAgentCoreContext`. Trace how workload access tokens are selected for the ECS/3LO use case. Done means the decorator accepts a workload identity name and uses its token without requiring local auth settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100