elastic / elastic/beats

[Security Alert] Exposed API key(s) detected: AWS Access Key

Open
#49,485 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs_team
Dominant language
Go
Stars
12.7k
Forks
5k
Avg merge
2d 1h
Merged PRs (30d)
370

Description

Hi,

An automated responsible-disclosure scan found pattern(s) matching the following API key type(s) in this file:

https://github.com/elastic/beats/blob/010854641205f1464dd6bbae560b49966a8339b2/docs/reference/filebeat/filebeat-input-httpjson.md

Keys detected
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 or 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

Open the contributing guide

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.

Research direction

Inspect docs/reference/filebeat/filebeat-input-httpjson.md at the referenced commit and review its git history for the detected AWS Access Key. Follow the alert's revocation, removal, history-purge, and dependent-service rotation steps; done means the credential is revoked and absent from the current file and repository history.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
documentation, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.