Non-user applications can create signed URLs, see Creating Signed URLs with 
a Program 
<https://cloud.google.com/storage/docs/access-control/create-signed-urls-program>.
 
You can do that in App Engine, if you want to enforce some kind of business 
logic, or let the external app create the signed URL by itself. With that 
approach the actual upload would go directly into the GCS bucket, without 
GAE in the middle.

However, if you don't need to return the unique ID in the response of the 
upload, you could consider to use a Google Cloud Function (Node.js and 
triggered by events in a GCS bucket, such as after an object is written 
into the bucket). The function gets the metadata of the written object and 
can create the unique ID and can write it to Cloud Datastore, for example, 
or to the custom metadata of the GCS object. For details see GCF's Cloud 
Storage Tutorial <https://cloud.google.com/functions/docs/tutorials/storage>
.

On Thursday, July 12, 2018 at 6:03:20 AM UTC+2, Parth Mishra wrote:
>
> I have a standard environment service that is handling HTTP POST requests 
> of images. It basically just creates a unique ID for them based on some 
> request metadata and then uploads to Cloud Storage.
>
> My question is, is GAE the right choice to handle this? I'll be getting 
> ~70K of these images (less than an MB each) throughout the day with various 
> peak and slow traffic times. I cant' generate a signed URL since the 
> application sending the request is an external, non-user application. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/91f19167-e817-4cf1-8e89-f404d0c9effb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to