opensearch-project / opensearch-project/data-prepper

Support proxy in OpenSearch source

Open
#5,422 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
374
Forks
354
Avg merge
3d 18h
Merged PRs (30d)
8

Description

Is your feature request related to a problem? Please describe.
I have a pipeline that reads from an OpenSearch index and writes in another one. That OpenSearch server is behind a proxy, so I need to configure it in the source and the sink

Describe the solution you'd like
I think the best solution is adding a proxy to the opensearch source:

source:
  opensearch:
    ...
    proxy: https://myproxy:8080

Or within the connection field:

source:
  opensearch:
    ...
    connection:
      proxy: https://myproxy:8080

Describe alternatives you've considered (Optional)

  • proxy field in the opensearch source, or in the connection subfield
  • proxy field in the data-prepper-config.yaml
  • Environment variable

Additional context
The proxy configuration is already supported for the opensearch sink. It was reported in #300 and implemented in #479

Thank you very much in advance!
I know how hard is maintaining an open source project, so if you need help, I can try to implement this

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

Start by examining the existing OpenSearch sink proxy support referenced in #300 and #479, then compare it with the OpenSearch source and connection configuration. Confirm the intended proxy placement and verify that a source-to-index pipeline can use the proxy while preserving existing sink behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, data-engineering
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.