Support existing IAM roles for runtime container-build infrastructure
维护者通常 1 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 54/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- aws, typescript
- 领域
- cloud, devops, infrastructure, security
调研方向
Start by tracing the agentcore add runtime command through its configuration handling, then inspect the @aws/agentcore-cdk runtime and container-build integration. Use agentcore.json to verify that supplied ARNs persist through build and deploy operations, and identify where shared CodeBuild configuration is validated. Done means all three supplied roles are imported without permission changes, omitted roles still trigger automatic creation, conflicts are rejected clearly, and tests and required trust/permission documentation are added.
由索引模型根据 Issue 内容生成。
描述
Description
agentcore add runtime --role-arn supports an existing runtime execution role. Container deployments still create two additional roles: a CodeBuild execution role and a Lambda execution role for the container-build handler.
This blocks container deployments in environments where IAM roles must be provisioned centrally.
Allow users to supply these roles when adding a runtime. Proposed flag names:
agentcore add runtime \
--name myAgent \
--language python \
--role-arn <runtime-role-arn> \
--container-build-role-arn <codebuild-role-arn> \
--container-build-handler-role-arn <lambda-role-arn>
Persist the ARNs in agentcore.json and expose equivalent configuration in @aws/agentcore-cdk.
Import supplied roles without modifying their permissions. Preserve automatic role creation when the options are omitted.
Acceptance Criteria
- Supplying all three roles produces no IAM roles or policies for the runtime or its container-build infrastructure.
- The configuration survives subsequent build and deploy operations.
- Shared CodeBuild infrastructure handles supplied roles consistently across runtimes and rejects conflicting configuration clearly.
- Documentation specifies required trust relationships and permissions for each role.
- Tests cover supplied roles, default role creation, and conflicting shared-build configuration.
Additional Context
This covers runtime container-build infrastructure. CDK bootstrap remains a separate prerequisite for environments that prohibit role creation.
- 主要语言
- TypeScript
- 星标
- 307
- 派生
- 107
- 平均合并
- 18 小时 56 分钟
- 30 天内合并 PR
- 166
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
aws/agentcore-cli 的其他 Issue
-
`agentcore dev` container fails with LoginTokenLoadError when using `aws login` credentials可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭bug
难度 2/5 1-3 小时 新手友好度 80/100
aws/agentcore-cli#2606 · 4 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
aws/agentcore-cli#2538 ·
维护者通常 1 天内回复
-
[Refactor] project add credentials payment does not match Connector regex可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 68/100
aws/agentcore-cli#2533 · 3 条评论 ·
维护者通常 1 天内回复
-
ci: skip CI jobs for release commits可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
aws/agentcore-cli#2392 ·
维护者通常 1 天内回复
-
bug documentation
难度 2/5 1-3 小时 新手友好度 74/100
aws/agentcore-cli#1241 ·
维护者通常 1 天内回复
查看 aws/agentcore-cli 的全部 Issue
相似的 Issue
-
calcite-ui-icons enhancement impact - p3 - not time sensitive needs triage
难度 2/5 1-3 小时 新手友好度 67/100
Esri/calcite-design-system#15467 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
diegosouzapw/OmniRoute#18390 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
-
难度 1/5 1-3 小时 新手友好度 86/100
guilhermerodz/input-otp#157 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
davidjerleke/embla-carousel#1414 ·
维护者通常 4 天内回复