Sign CNAME with pre-signed url

[jerry3323]

Describe the feature

I'm trying to find a way how I can use cname when creating presigned url with java sdk v2

use the same way in aws/aws-sdk-java#1498

Use Case

PresignedGetObjectRequest presignedRequest =
s3Presigner.presignGetObject(r -> r.getObjectRequest(get -> get.key("JooqConfiguration.java"))
.signatureDuration(Duration.ofDays(6)));

but i get a error result .

Caused by: java.lang.IllegalArgumentException: Parameter 'Bucket' must not be null
at software.amazon.awssdk.protocols.xml.internal.marshall.SimpleTypePathMarshaller.lambda$static$0(SimpleTypePathMarshaller.java:46)
at software.amazon.awssdk.protocols.xml.internal.marshall.XmlProtocolMarshaller.doMarshall(XmlProtocolMarshaller.java:106)
at software.amazon.awssdk.protocols.xml.internal.marshall.XmlProtocolMarshaller.marshall(XmlProtocolMarshaller.java:80)
at software.amazon.awssdk.protocols.xml.internal.marshall.XmlProtocolMarshaller.marshall(XmlProtocolMarshaller.java:49)
at software.amazon.awssdk.services.s3.transform.GetObjectRequestMarshaller.marshall(GetObjectRequestMarshaller.java:51)
... 5 more

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS Java SDK version used

2.27.21

JDK version used

11

Operating System and version

ios

[bhoradc]

Hello @jerry3323,

Thank you for submitting the feature request.

As per AWS S3 documentation, when using a CNAME record to access an S3 bucket, the CNAME record name and the S3 bucket name must be the same. This is because Amazon S3 uses the hostname to determine the bucket name, and it is unaware of the CNAME mapping used to resolve the request.

Are you able to follow the mentioned guideline and validate if you still face any issues generating the pre-signed URL using v2 SDK?

Kindly share how the generated URL looks like in case you still see an issue.

Regards,
Chaitanya

[github-actions]

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.