AgentCore provides no information on AWS account or profile being used
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 38/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- aws, typescript
- 领域
- cli, cloud, documentation
调研方向
从 AgentCore CLI 的 status/dev 入口点以及 issue 中链接的 getting-started CLI 文档开始；查看 #1727 以了解 profile 支持的背景。完成标准是文档说明本地 AWS 访问方式，并且 status 能识别解析出的 account 或 profile，同时根据报告的 Windows 流程检查行为。
由索引模型根据 Issue 内容生成。
描述
Description
The AgentCore "getting started" instructions are not clear that "local" development actually accesses AWS, and critically apparently provides no indication of which AWS account is being used.
Steps to Reproduce
Follow the instructions for Get started with the AgentCore CLI:
agentcore create --name MyAgent --framework Strands --protocol HTTP --model-provider Bedrock --memory none
cd MyAgent
agentcore status
Status says:
AgentCore Status (target: )
Agents
MyAgent: Local only
Then run:
agentcore dev
Enter a question, e.g.:
What are the benefits of uv over pip?
Expected Behavior
- "Local only" means no server access.
- If an AWS account is accessed,
agentcore statusshould indicate which account is being accessed.
Actual Behavior
- An error occurred, which apparently means that "local only" is not "local only".
Error: An error occurred (AccessDeniedException) when calling the ConverseStream operation: Your account is currently being verified. Verification normally takes less than 2 hours. Until your account is verified, you may not have access to this operation. If you are still receiving this message after more than 2 hours, please let us know by writing to [email protected]. We appreciate your patience.
- There is no information about which AWS account is being accessed, and no obvious way to find out.
CLI Version
0.27.0
Operating System
Windows
Additional Context
AWS best practices requires setting up multiple accounts. Users need to be able to know which account is being accessed. This issue is a compounding of the critical oversight of #1727: the --profile switch is not implemented, and it's not even clear if AWS_PROFILE is supported. Therefore, when the "local" setup tries to access something that isn't local, users need to know what it's trying to access.
- Improve the documentation to explain that "local" (apparently) only refers to the agent harness; an AWS account is still being accessed.
- Implement
--profileandAWS_PROFILEfrom #1727. - Provide visibility in
agentcore statusto indicate which profile is being resolved.
- 主要语言
- TypeScript
- 星标
- 291
- 派生
- 96
- 平均合并
- 20 小时 50 分钟
- 30 天内合并 PR
- 214
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
aws/agentcore-cli 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
aws/agentcore-cli#2395 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
aws/agentcore-cli#2392 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
aws/agentcore-cli#2267 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
aws/agentcore-cli#2258 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
aws/agentcore-cli#2176 ·
维护者通常 1 天内回复
查看 aws/agentcore-cli 的全部 Issue
相似的 Issue
-
ADD openalgo未关闭template
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
factory-active factory-automatic task-bug-reproduction-success task-identify-harness-labels-done task-identify-issue-type-done
难度 2/5 1-3 小时 新手友好度 90/100
维护者通常 1 天内回复
-
bug Needs: Triage :mag:
难度 2/5 1-3 小时 新手友好度 84/100
microsoft/fluentui-contrib#671 ·
-
难度 2/5 1-3 小时 新手友好度 88/100
sveltejs/acorn-typescript#150 ·
-
难度 2/5 1-3 小时 新手友好度 78/100