opensearch-project / opensearch-project/data-prepper
[BUG] HTTP and Prometheus not working when SigV4 Enabled
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Describe the bug
HTTP and Prometheus not working when SigV4 Enabled. HTTP plugin code - throws 408 Exception and Prometheus we see 403 ERROR
To Reproduce
Steps to reproduce the behavior:
Aws_sigv4 enabled - I don’t see the code sending request to HTTP endpoint
- Exceptions are not seen in the dataprepper console
- Pipeline is not posting any data to endpoints
- Cloudwatch logs are clean and see no data at all
Expected behavior
Expected the data to be posted to Lambda with SigV4 and AMP
Screenshots
Environment (please complete the following information):
Local testing
Contributor guide
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 reproducing the issue locally with aws_sigv4 enabled, using the HTTP and Prometheus paths described in the report. Trace why requests are not reaching the HTTP endpoint or AMP, and verify that Lambda and AMP receive data while failures are visible in Data Prepper or CloudWatch logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java, prometheus
- Domain
- api, backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100