vishwaggupta opened a new issue, #34781:
URL: https://github.com/apache/airflow/issues/34781

   ### Description
   
   Currently LambdaInvokeFunctionOperator doesn't provide option to overwrite 
read_timeout settings which is defaulted to 60 seconds specially for managed 
services like AWS MWAA. LambdaInvokeFunctionOperator timeout if Lambda function 
execution time is more than 60 seconds. Customers have to change to other 
options like python operator with boto3 based execution.
   
   ### Use case/motivation
   
   Providing option to overwrite read_timeout will enable customers to use 
LambdaInvokeFunctionOperator in cases when AWS lambda function execution time 
is more than 60 seconds, since it's not well documented in open source 
community project teams discover this based on DAG step failures. Solving this 
will save time/effort and create better experience for the project teams.
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to