Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS S3 to S3 transfer without Dataplane as middleware #231

Closed
rafaelmag110 opened this issue Feb 14, 2024 · 3 comments
Closed

AWS S3 to S3 transfer without Dataplane as middleware #231

rafaelmag110 opened this issue Feb 14, 2024 · 3 comments
Labels
feature_request New feature request, awaiting triage

Comments

@rafaelmag110
Copy link
Contributor

Feature Request

During an AWS S3 to S3 transfer using the Connector, the current transfer behaviour is for the S3 DataSource to get the transfer payload from the source bucket into memory and push the payload into the destination bucket. This creates a bottleneck in the dataplane as the payload can consume all the host memory resources.

As a feature request, i'd like to explore the idea of levering the AWS S3 API to trigger a direct transfer from one bucket to another, without any payload even reaching the dataplane. In this case, the connector would act as a transfer coordinator only.

This only applies to AWS S3 to S3 transfers.

Which Areas Would Be Affected?

S3 DataSource and Sink.
S3 Provisioners would have to be changed aswell to correctly setup the environment for the transfer (permission management).

Why Is the Feature Desired?

Benefits in performance.

Solution Proposal

N/A

Copy link

Thanks for your contribution 🔥 We will take a look asap 🚀

Copy link

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale label Feb 29, 2024
@ndr-brt ndr-brt added feature_request New feature request, awaiting triage triage all new issues awaiting classification and removed stale labels Feb 29, 2024
Copy link

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale label Mar 15, 2024
@ndr-brt ndr-brt removed stale triage all new issues awaiting classification labels Mar 20, 2024
@eclipse-edc eclipse-edc locked and limited conversation to collaborators Mar 25, 2024
@mspiekermann mspiekermann converted this issue into discussion #270 Mar 25, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
feature_request New feature request, awaiting triage
Projects
None yet
Development

No branches or pull requests

2 participants