Hi @silk tinsel this is currently a limitation of how Amplify and S3 work today. The URL is presigned in order to keep you files and data protected. We are currently tracking this and other related feature requests here - https://github.com/aws-amplify/amplify-js/issues/9418
Please feel free to add any additional context about your use case to the issue