-
Notifications
You must be signed in to change notification settings - Fork 634
Closed
Labels
closed-for-stalenessp3This is a minor priority issueThis is a minor priority issueresponse-requestedWaiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.v2-v3-inconsistencyBehavior has changed from v2 to v3, or feature is missing altogetherBehavior has changed from v2 to v3, or feature is missing altogether
Description
Pre-Migration Checklist
- I've read the Migration Guide.
- I've reviewed the upgrading notes and major version differences mentioned in
UPGRADING.md
. - I've checked AWS Forums and StackOverflow for similar migration issues.
Which JavaScript Runtime is this issue in?
Node.js (includes AWS Lambda)
AWS Lambda Usage
- Yes, my application is running on AWS Lambda.
- No, my application is not running on AWS Lambda.
Describe the Migration Issue
We are using the @aws-sdk/s3-request-presigner package to generate pre-signed URLs for uploading and downloading objects from S3. When used publicly (without a proxy), everything works as expected. However, when routing traffic through a proxy, the operations fail, and I'm unable to generate or use the pre-signed URLs properly.
How can we configure this to work correctly when using a proxy? Can you help with this?
Code Comparison
No response
Observed Differences/Errors
Additional Context
No response
Metadata
Metadata
Assignees
Labels
closed-for-stalenessp3This is a minor priority issueThis is a minor priority issueresponse-requestedWaiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.v2-v3-inconsistencyBehavior has changed from v2 to v3, or feature is missing altogetherBehavior has changed from v2 to v3, or feature is missing altogether