Hmm…thanks for the thoughts guys. I’ve been reading up at the Amazon S3 forums, and I’m pretty sure now that my initial hunch was right. My server would still be the one processing the upload. It just saves it to another place. So, I’m pretty sure that the upload_max_filesize setting sticks. It not a limit imposed by Amazon, it’s just the capability of the uploading server.
I did a few tests with changing my PHP settings, and it seems like that is the case.
I’m thinking of a solution with coupling Amazon S3, Google Gears and EE for uploading large files. I saw an extension yesterday in the Extension forums that used the new version of Google Gears to split large files into chunks and then process them. Perhaps (and I have no idea if this is possible at all), I would be able to split a file, reassemble it on my server and then send it off to Amazon S3 and delete whatever local assets are left over.
If nothing else, it’ll be a learning experience. I’ll 100% be posting about this as I make any progress.
If anyone has any hints, tips or wants to double team this thing, I’d of course welcome the help.