TopologyMapping / TopologyMapping/network-security
Extend ScoutTask to control AWS targets
Open
Nobody has claimed this yet.
scout
- Dominant language
- Jupyter Notebook
- Stars
- 0
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
The current implementation always runs Scout on the account configured in the credentials file passed the ScoutConfig. We should allow a task to:
- Overwrite the access keys used for authentication
- Specify a Role to be assumed before running Scout
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating ScoutTask and ScoutConfig, then trace how the credentials file is used when Scout runs. Done means a task can override authentication access keys and specify a role to assume before running Scout; no tests or source files are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100