I have done some forum digging on the site and failed to find a result so thought to make a new post seeking to answer to the (hopefully simple) question: Where do our files go when we sleep?
I have been running some iframe instances of my shapediver script and receiving a notification when someone uploads a file, but when I attempt to access the S3 bucket my permission is denied.
My best guess is that this a ShapeDiver S3 Database that is storing these files, meaning I am not a registered user (obviously) and am unable to do anything further with them.
Is it possible to redirect this storage to an S3 instance that I do manage so I can act on these files?
Has the shapediver done any work on the automation of data import/export storage and management (meaning not copying the URI into the import command) that I might have missed on the forums?
I wonder which type of notification and S3 bucket you are referring to. Please explain.
You can of course use an S3 bucket of your own, or any other online storage service that allows you to create publicly accessible links. These links can carry a signature, such that they are only accessible for a short amount of time. Then you feed these URLs to one of the Import components.
The files that I am referring to throughout are files that users submit via ImportGeometry parameters in my ShapeDiver script. Through my website (which is hosting my iFrame) I can see a submitted file passing though the site but it disappears after a few days and I do not have access to it when I visit the s3 link. This is referring to a ShapeDiver owned bucket with a specific signature type? Is there a simple way to change this to a bucket that I own?
Based on your last chunk, I am understanding that I can have my users upload a file somewhere else in the site to my own S3 bucket and then return that file through the URI input of an Import component. This is a potential work around, although I would love to have all ShapeDiver submitted files in the same bucket as the users other data.
Curious if there is documentation on this that I may have missed!