I suspect someone responded privately, but just in case I'll provide some quick advise, for what its worth, and you can reply privately or on Slack to keep the listserv clean.
You said earlier that, "I am not storing any images on iiif Server". This is the problem. IIIF URLs simply won't work with any image storage (S3 or localhost or other) without a IIIF image server to translate the coordinates, tiles, etc. Perhaps it's confusing because OpenSeadragon supports IIIF. But keep in mind that OpenSeadragon is a document viewer, and NOT an image server.
Regarding S3 for image storage, it can be done with IIIF image servers but you may need to cache the images on your image server. As far as I know, S3 cannot deliver parts of image data (i.e., its all or nothing, so they can't grab individual tiles from inside a JP2 or TIF), which paralyzes the main elements of IIIF. Since our entire infrastructure is on AWS, we use an auto-scaling Cantaloupe cluster (i.e, our IIIF image servers) bound with EFS (Elastic File System) to S3 and it works brilliantly. We also store our original raw TIFs on AWS Glacier. So the progression is from Glacier -> S3 -> EFS--Cantaloupe -> web application. But this is a much bigger discussion as it requires advanced configuration on AWS. I recommend directing specific technical questions to the Slack channel.
I hope this makes sense.
Regards,
Danny
Daniel T. Michaels, Ph.D.
Chief Technology Officer
National Institute for Newman Studies
211 N. Dithridge St.
Pittsburgh, PA 15213