Skip to content
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

finalizeMultipartUpload is throwing 404 error #3111

Closed
1 task done
savan143 opened this issue May 14, 2024 · 3 comments
Closed
1 task done

finalizeMultipartUpload is throwing 404 error #3111

savan143 opened this issue May 14, 2024 · 3 comments
Assignees
Labels
closed-for-staleness guidance Question that needs advice or information. response-requested Waiting on additional info or feedback. Will move to "closing-soon" in 5 days.

Comments

@savan143
Copy link

savan143 commented May 14, 2024

Upcoming End-of-Support

  • I acknowledge the upcoming end-of-support for AWS SDK for Java v1 was announced, and migration to AWS SDK for Java v2 is recommended.

Describe the bug

We are utilizing multipart upload feature in our application. It has 4 steps.

  1. InitializeMultipartUpload
  2. GenerateS3SignedUrl
  3. Upload Parts
  4. FinalizeMultipartUpload

Here whole flow was working fine before we enabled public access block on our S3s.
After enabling this public access block we are doing all transaction using CF url instead of direct s3 url. Here First 3 steps are working fine where 4th step(FinalizeMultipartUpload) is throwing below error.

The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed. (Service: Amazon S3; Status Code: 404; Error Code: NoSuchUpload; Request ID: DF9DESQHKG183Q2D; S3 Extended Request ID: GAVKk1LSbjHWN6pMDw3lA3b8YjF8crE+xg8YyVjPiVxnv5wSrx1PqBcnpk3ry90r5HGOof11GaYxyz=; Proxy: null)

Can someone please help us finding the missing logic here if we are missing anything?

Current SDK version we are using is 1.12.410.

Expected Behavior

It was working fine before public access block and that's what we are expecting.

Current Behavior

FinalizeMultipartUpload method is throwing below error.

The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed. (Service: Amazon S3; Status Code: 404; Error Code: NoSuchUpload; Request ID: DF9DESQHKG183Q2D; S3 Extended Request ID: GAVKk1LSbjHWN6pMDw3lA3b8YjF8crE+xg8YyVjPiVxnv5wSrx1PqBcnpk3ry90r5HGOof11GaYxyz=; Proxy: null)

Reproduction Steps

Mentioned steps in description which we are following currently in our application.

Possible Solution

No response

Additional Information/Context

No response

AWS Java SDK version used

1.12.410

JDK version used

java-base:17-temurin

Operating System and version

Java

@savan143 savan143 added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels May 14, 2024
@savan143
Copy link
Author

@debora-ito
Copy link
Member

@savan143 The error means S3 is saying that the uploadId you provided in the FinalizeMultipartUpload step was not found on the service side.

If the flow worked fine when accessing S3 directly, but the exact same code is not working when using Cloudfront, you should check if any request attribute is being altered in the communication to S3 after the change. I suggest you generate more detailed logs, like verbose wirelogs, of the request attribute values before and after the change, to compare and help identify the difference.

@debora-ito debora-ito added guidance Question that needs advice or information. response-requested Waiting on additional info or feedback. Will move to "closing-soon" in 5 days. and removed bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels May 17, 2024
@debora-ito debora-ito self-assigned this May 17, 2024
Copy link

It looks like this issue has not been active for more than five days. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please add a comment to prevent automatic closure, or if the issue is already closed please feel free to reopen it.

@github-actions github-actions bot added closing-soon This issue will close in 2 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will close in 2 days unless further comments are made. labels May 28, 2024
@github-actions github-actions bot closed this as completed Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-for-staleness guidance Question that needs advice or information. response-requested Waiting on additional info or feedback. Will move to "closing-soon" in 5 days.
Projects
None yet
Development

No branches or pull requests

2 participants