You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The library should be smart enough to use path style when bucket name includes dot. It can do so. This allows the same S3 client instance can be used to interact with multiple buckets, without forcing path style for all the buckets.
This is inconsistent with multipart upload, the location of multipart upload output will use path style when bucket name includes dot, even if forcePathStyle is not set.
This is inconsistent with the behavior of V2.
Regression Issue
Select this option if this issue appears to be a regression.
SDK version number
@aws-sdk/lib-storage@3.679.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
Checkboxes for prior research
Describe the bug
Related issue:
#5490
Related Code
https://github.com/aws/aws-sdk-js-v3/blob/main/lib/lib-storage/src/Upload.ts#L171-L181
Why I think this is a bug:
forcePathStyle
is not set.Regression Issue
SDK version number
@aws-sdk/lib-storage@3.679.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
v18.17.0
Reproduction Steps
Use an s3 bucket with dots in its name
Observed Behavior
the location returned is not an accessible url
eg. https://example.bucket.s3.ap-south-1.amazonaws.com/key
Expected Behavior
it should use path style, eg. https://s3.ap-south-1.amazonaws.com/example.bucket/key
Possible Solution
No response
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: