After uploading a file as public with aws storage, I havent public access to the object URL.

[rallona]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework

React, Next.js

Amplify APIs

Authentication, Storage

Amplify Version

v6

Amplify Categories

storage

Backend

None

Environment information

# Put output below this line

AWS AMPLIFY V6

Describe the bug

I have uploaded an image using aws amplify storage. The upload is correct and I can see the image in the S3 bucket inside a /public folder, but I am unable to get the URL to that image.

I have used the getUrl method, but only gives me the signed URL, which has an expiring date. I need a public URL without expiration date.

Is this possible to achieve? Thanks!

Expected behavior

I want to get the public URL of the image that I have just uploaded.

Reproduction steps

Using the getUrl method

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

[cwomack]

Hello, @rallona and thanks for opening this issue. Right now, the maximum timeframe that a download URL can be set for is 1 hour out of the box with the getUrl API. As such, I'll mark this as a feature request rather than a bug or question.

Not sure if you're wanting to dig into using the aws-sdk, but it does look like there's an ability to have up to 7 days before the signed URL expires. Either way, we'll mark this as a feature request for the Amplify side and follow up with any further questions or progress from here!

[cwomack]

After reviewing this further internally, we're going to consolidate this issue into #9418. Please follow that issue going forward for updates on this feature and feel free to add any comments, additional context, or upvotes to it to help with traction. Thank you!