However, I am slightly confused as to the best way to distribute access to these files.
I am assuming the only people who will see the download link URL's will have received it 'after' purchase either by email or direct access to their purchases from the download page I create housing the download link(s).
Therefore, I am assuming the bucket files should have 2 separate permissions set:
grantee: admin_user (me) - [Check]open/download [check]view permissions [check]edit permissions
grantee: Everyone - [check]open/download [check]view permissions [no] edit permissions
I ask only because, I saw a video suggesting NOT to make buckets 'accessible' by everyone due to sharing and piracy issues, but instead, concerned using expiring download links by adding PHP expiring download links.
(*I don't think I'll be needing to do all that much worrying about who is downloading for simplicities sake, right?)
So, to keep things simple, is it safe to say; if my product download URL's will be delivered via email and/or only accessible through a Thank-You Download page after purchase... I should then just use the 'Everyone URL' permissions and the link provided inside my S3 bucket properties, correct?
I did test the download link, and the 'download' options window does open the download dialog window - so the link appears to be working.
Lastly, because this was my 1st S3 bucket set up, and I am just now getting familiar with the uploading and delivery process... I cheated and just 'uploaded' the entire 575mb product (containing several zip files inside) as just one zip file.
To change this, I could essentially break-down the files and nest each individual zip file under the product (bucket) as follows:
S3 Bucket Name: kickassgraphicsbundle
Naturally, I'll mask the Download Link Titles on my download page (So they are more presentable aesthetically), but I notice many times when I buy/download larger digital based products or software, they have more than one download link... which I'll likely 'break the product down into bite-size downloads...
But, I too notice, whenever I download a purchase from a seller who is using AWS or an S3 bucket... their links are almost always... a lot longer with a series of numbers, letters, % symbols, etc... then the ones I am generating in my AWS S3 account, why is this?
Why are my URL's showing so clean in my S3 bucket?
My apologies for all the questions, as every time I seek instruction from within AWS platform, I end up questioning 'if' I should be using CloudFront instead?, or if I need Cloudberry? or should I create an elastic virtual server in EC2 first?...etc