6

My API server has a very limited disk space(500MB) and memory(1GB). One of the API calls that it gets, is to receive a file. The consumer calls API and passes URL to be downloaded.

The "goal" of my server is to upload this file to Amazon S3. Unfortunately, I can't ask the consumer to upload the file directly to S3(part of requirements).

The problem is, sometimes those are huge files(10GB) and saving them to disk and then uploading it to S3 is not an option(500MB disk space limit).

My question is, how can I "pipe" the file from the input url to S3 using curl Linux program ?

Note: I was able to pipe it in different ways but, either it first tries to download the whole file and fails or I hit memory error and curl quits. My guess is that the download is much faster than the upload, so the pipe buffer/memory grows and explodes(1GB memory on server) when I get 10GB files.

Is there a way to achieve what I'm trying to do using curl and piping ?

Thank you, - Jack

Joe
  • 61
  • 3
  • How is your server implemented? Most programming languages should allow you to "stream in/stream out" in the code so that you're not keeping too much in memory at a time. If that's not an option then your best bet may be to add a modest sized EBS volume (say 100GB) to the instance and use that as a temporary staging area. – stdunbar Aug 10 '17 at 17:41
  • @stdunbar - without going into too much internal details, I prefer to "invoke" curl and do the job. If it's feasible, great! If not, I will have to figure other ways and I will take your suggestion. Ty – Joe Aug 10 '17 at 17:55

1 Answers1

1

Another SO user asked a similar question about curl posts from stdin. See use pipe for curl data.

Once you are able to post your upload stream from the output of the first curl process's standard output, if you are running out of memory because you are downloading faster than you can upload, have a look at the mbuffer utility. I haven't used it myself, but it seems to be designed for exactly this sort of problem.

Lastly, if all else fails, I guess you could use curl's --limit-rate option to lock the transfer rates of the upload and download to some identical and sustainable values. This potentially underutilizes bandwidth, and won't scale well with multiple parallel download/upload streams, but for some one-off batch process, it might be good enough.

terafl0ps
  • 684
  • 5
  • 8