apachecn / apachecn/apachecn-devops-zh
[Security Alert] Exposed API key(s) detected: AWS Access Key
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
An automated responsible-disclosure scan found pattern(s) matching the following API key type(s) in this file:
**https://github.com/apachecn/apachecn-devops-zh/blob/72ae6d5a6bd908b4395bec8fef898277ff861175/docs/docker-aws/03.md**
### Keys detected
- **AWS Access Key** → revoke at https://console.aws.amazon.com/iam
### Recommended actions
1. **Revoke each key immediately** using the links above
2. **Remove the key(s) from the file** and commit the change
3. **Purge from git history** — keys remain accessible in old commits even after deletion. Use [`git filter-repo`](https://github.com/newren/git-filter-repo) or [BFG Repo Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)
4. **Rotate any dependent services** that used these credentials
> This is an automated alert. No keys were tested, validated, or used in any way. If this is a false positive, please close this issue.
---
*Sent by a responsible disclosure scanner to help protect accidentally exposed credentials.*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with docs/docker-aws/03.md at commit 72ae6d5a6bd908b4395bec8fef898277ff861175 and inspect the reported AWS Access Key. Revoke the key, remove it from the file, purge it from git history with git filter-repo or BFG Repo Cleaner, and rotate dependent services; done means the credential is revoked and no longer available in the repository history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, git
- Domain
- cloud, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100