I’d love to hear what the folks at Wappler think is the best methodology with S3 to achieve what I wish to do…
The user experience I need for a multi-user app is:
The user uploads a file which is to be stored in my AWS S3 bucket.
During the process, the file is given a unique name such as hUbdgU7hdGF.jpg
In a database of filenames, I record the exact path to their file, which they can they link to when they send emails from within my app… so a path like mys3bucket.amazonsurl.com/hUbdgU7hdGF.jpg
I’ve never really worked with files in Wappler before, so am starting from a “file newbie” perspective. Was waiting for the S3 moment to start!
So from what I can see, it looks like I’ll need to do something like this:
Upload the file (say my_image.jpg) to the server.
Rename the file on the server to xyz.jpg
Upload the file from the server to S3.
Store the filename in my database as mys3bucket.amazonsurl.com/xyz.jpg
In which case I won’t be using App Connect S3, but I’ll be using Server Connect S3.
Is this the best way to achieve what I am looking for?
Normally you give the filename as “key” to the S3 functions and that is what you store.
You can however just generate the key yourself using a date stamp or other hash to make it unique.
Just pass that to S3 as key and it will be used to save the file there under that name.