How can I reference a file from the Losant files repository to be uploaded to AWS using this node?
the content box won’t allow me to use the {{file ‘path/file’}} helper
The {{file 'path/file'}} helper results in the file link, not the file content. The AWS S3: Put Node puts the contents of the file to an S3 bucket. Currently there is not a way to get the contents of an Application File.
You could, however, use an HTTP Node to send your file to AWS S3, but you will be limited to file sizes less than 5MB.
Thank you,
Heath
Yeah, this file is around 60Mb so that won’t work.
I was reading Export device state to CSV > FTP
Any new options for me today?
I guess I could have the other side download from the files.onlosant.com path , right?
Hi,
In our usage scenario, we need to upload a file to a private AWS S3 bucket, but these files can exceed the limit accepted by the workflow. In this case, it would be interesting to allow returning the signed URL so that the file can be uploaded by the browser, as in the API File: Post (but in this case the upload happens to the platform’s Files).
Thanks!
That’s a good feature request; I’ll log that for you. Thanks.
How are you getting around this in the meantime? Are you able to use a Lambda Function (via the AWS Lambda Node) or hit an AWS API Gateway endpoint (using the HTTP Node) to generate the signed URL?
Hi,
We created a Lambda Function that receive as input the string to sign and outputs the signature.
But we believe that this is not the better way to perform the signature process.
The AWS Lambda Node signs internaly to invoke the Lambda Function and the lambda signs to the Workflow.
The signature is computed twice and this is not a good path.
We talked about this issue and we believe that a good feature is to include a checkbox in all AWS S3 nodes asking if the output is effectivily upload the file or just a signed URL.
Thanks.