How do I go about getting the output returned by another function I invoked from the main function?

By -

This will be a bit hard to explain but here we go.

I have an AWS Lambda function that uses youtube-dl to download videos from YouTube, then it uploads it to S3 and returns the S3 link for download. Let's call it function1 for reference.

I connected it to API Gateway, I then discovered that the API Gateway in AWS has a timeout of 29 seconds. That means, if I trigger the Lambda function from the API Gateway with a YouTube URL to download, it will wait for 29 seconds, if it didn't get any output it will timeout, terminating the function with it.

Of course, downloads usually take way more than 29 seconds and this limit is annoying.

I got an idea to fix that, created another Lambda function (function2). I linked it to the API Gateway, so then, I can make an http request to function2 with the YouTube URL, then function2 would invoke function1 passing the URL to it.

However, I'm running into a problem now. How do I get the S3 link that function1 returns?

What happens is, I make a request to function2 with the URL, then it passes it to function1, function2 will return a string saying that it's downloading. However I'm really not sure on how to go about getting the S3 link from the function that downloads the video and then uploads it to S3.

I thought about putting the S3 link in an S3 bucket, but then how does the client know that the function put the link there? The only way I can think of is to make the client make requests over and over to see if the link is there and I honestly really don't want to do unnecessary requests.

Oh, and making function2 wait for a response from function1 when invoking it would defeat the purpose of this workaround.

I'm using Python by the way, if it makes any difference.



from Recent Questions - Stack Overflow https://ift.tt/2G6Skes
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more