Discussions
URL for CreateAsset
I am using lambdas and have a five minute window to execute my code. When our assets are larger than around 5 GB the upload time exceeds this limit. The response from the MultiPartUpload provides the URL that is to be provided to the CreateAsset API, however I will likely not get the response in time. There is also the problem of refreshing the credentials when the upload takes longer than an hour. Can I write my own upload from our S3 bucket to MediaSilo's S3 bucket and then call CreateAsset using the URL that I used to write the asset? Is there some other way to get the URL from MediaSilo if I get a S3 bucket notification that the asset has been uploaded by one of your APIs?
I may be confused about when I get the URL. Looking at the documentation again it appears that the URL to be used for CreateAsset is provided when the upload ticket is created rather than with the response of the actual upload. If this is the case, then the remaining problem is refreshing the credentials in MultiPartUpload. It appears that the Aspera enabled upload (https://api.mediasilo.com/v3/aspera/upload) does not have this credential refresh problem. So if our account is upgraded to the Aspera enabled one I should be able to call the Aspera upload for the ticket, do a PUT to the provided URL, get an S3 bucket notification when the asset is uploaded, and then call the CreateAsset with the originally provided URL?
Janice Luncford, I would not recommend using lambda to upload content, a 5 min window is very small for moving files around, and though AWS does provide a throughput value it will not be consistent and you will end up with edge cases of files not making it. Our upload options are provided to clients when they do not have another option. We don't actually require that you use the upload ticket, our asset create process will accept any URL from any location, you are free to use your own S3 bucket and upload process, if the object is secured you will need to provide a signed URL that lasts long enough.
The upload ticket provides a URL which is the location you will upload the file to, this destination does not exist nor work until you complete the upload process, this URL is also unique in that you cant access it other then the PUT request for security reasons, our system knows how to handle these special URLs which is why we can provide them prior to the upload process.
Using the multi-part upload process you will need to refresh the credentials, this is required by AWS for uploading files larger then 5GB, and our Aspera offering is no longer available. However, as mentioned before you do not need to use our upload ticket process, our asset create only requires an accessible URL.
ο»Ώ