Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

security: fail closed on ambient AWS credential fallback

Open
#898 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@scottschreckengaust is already working on this.

Since Sep 15, 2026.

Assessment

This issue has not been assessed yet.

Description

approved security v1

Problem

agent/src/bedrock_creds_helper.py returns ambient compute-role credentials when the attribution file is missing, malformed, or STS credential issuance fails.

Repository-controlled code can invoke the helper with a nonexistent attribution file, parse the credentials written to stdout, and use the compute role outside the intended task boundary. The role currently has permissions that may expose cross-workspace provider secrets and shared task resources.

Required behavior

Credential issuance must fail closed whenever task attribution is absent, malformed, forged, or cannot be validated.

Ambient compute credentials must never be returned to repository-controlled processes.

Scope

  • Remove ambient credential fallbacks from agent/src/bedrock_creds_helper.py.
  • Ensure task identity comes from trusted, immutable state.
  • Reduce compute-role permissions to bootstrap-only access where possible.
  • Remove direct repository access to wildcard provider-secret and shared-state permissions.

Acceptance criteria

  • Missing attribution files return an error and no credential JSON.
  • Malformed and forged attribution files return an error and no credentials.
  • STS failures do not fall back to ambient credentials.
  • Tests verify repository UID execution cannot obtain ambient credentials.
  • IAM tests verify compute roles cannot read wildcard workspace secrets or modify shared concurrency state.
  • Bedrock calls continue to work through validated task identity.
Dominant language
TypeScript
Stars
154
Forks
48
Avg merge
3d 23h
Merged PRs (30d)
21

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/sample-autonomous-cloud-coding-agents

All issues in aws-samples/sample-autonomous-cloud-coding-agents

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.