Skip to content

feat(add-aws): skill for AWS CLI access in agent containers#2319

Closed
ira-at-work wants to merge 1 commit into
nanocoai:mainfrom
ira-at-work:feat/add-aws
Closed

feat(add-aws): skill for AWS CLI access in agent containers#2319
ira-at-work wants to merge 1 commit into
nanocoai:mainfrom
ira-at-work:feat/add-aws

Conversation

@ira-at-work
Copy link
Copy Markdown

Summary

  • Adds /add-aws skill: installs awscli in the agent container, wires the OneCLI CA bundle so TLS verification works through the credential proxy, mounts AWS credentials from OneCLI vault, and documents how to bypass the proxy for direct AWS endpoints.

Test plan

  • Follow SKILL.md on a fresh install with an AWS credential in OneCLI vault
  • Verify aws s3 ls works inside a container session
  • Verify TLS succeeds (no certificate errors) through the OneCLI proxy

🤖 Generated with Claude Code

Covers awscli installation, CA bundle wiring, credential mounting,
and OneCLI proxy bypass.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@gavrielc
Copy link
Copy Markdown
Collaborator

gavrielc commented May 7, 2026

Thanks for putting this together — the structure and troubleshooting coverage are really solid.

One issue we can't work around: the NO_PROXY bypass routes AWS traffic outside the OneCLI proxy. We understand there may be individual setups where someone decides that tradeoff is acceptable for them — but it's not something we can ship as part of the project. Closing for now.

@ira-at-work
Copy link
Copy Markdown
Author

fair enough. I will find some MCP solution or something. I don't like having the credentials seen by the agent either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants