[hotnops]

Documents the distinction between runtime authentication and organization collection strategy, generated profile chains, review and hardcoded-config workflows, runtime auth modes, and the meanings of overloaded AWS configuration names.

Validation: mint validate passed.

Jira: BED-10235

Summary by CodeRabbit

• Documentation
  • Clarified the distinction between runtime credential discovery and organization role assumption.
  • Explained that source_account refers to an AWS account ID, not a profile name.
  • Added guidance on generated AWS shared-config profiles, including storage, reuse, generation controls, and runtime authentication modes.
  • Updated the source-account strategy table to distinguish the collection role, runtime identity, and management role.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: db796fce-dc18-402a-b745-1f1921465743

📥 Commits

Reviewing files that changed from the base of the PR and between 2893799 and b43c83f.

📒 Files selected for processing: 1

• docs/openhound/collectors/aws/collect-data.mdx

Included review availability: This review used your included allowance. 4 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

Walkthrough

The AWS collector documentation now distinguishes runtime authentication from organization role assumptions. It describes generated profile configuration and clarifies the meaning of source_account, org_role_name, and management_role_name.

Changes

AWS collector documentation

Layer / File(s)	Summary
Runtime authentication and organization roles docs/openhound/collectors/aws/collect-data.mdx	The guidance describes generated profile behavior, configuration controls, and runtime authentication modes. It clarifies that source_account is an account ID and distinguishes the member role from the management role.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~4 minutes

Change: Other

Suggested reviewers: jeff-matthews

Merge Risk: ⚪ Minimal · up to b43c8

The documentation clarifies runtime authentication and organization roles. No concrete merge-blocking setup issue is established, so no PR-specific risk remains.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: documenting generated AWS authentication configuration.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{A rabbit reads the AWS guide,
And checks each profile by its side.
The roles now have their names made clear,
Runtime choices are written here.
It hops away with docs in stride.}

_{Comment @coderabbitai help to get the list of available commands.}

[jeff-matthews]

Thanks for the PR @hotnops!

Please consider my editorial suggestions in #486 to help prepare for publication.