Support executor_config on Lambda Executor #53994
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The executor_config for the Lambda executor will be plumbed through the Lambda invoke payload at the key "executor_config". We cannot use the Lambda ClientContext object because this is not supported on async Lambda invocations. When updating the docs for the Lambda executor I noticed the name was incorrect in the docs for the other AWS executors, so I've updated those as well.
boring-cyborg
bot
added
area:providers
kind:documentation
provider:amazon
o-nikolas
changed the title
vincbeck
approved these changes
Jul 31, 2025
potiuk
approved these changes
Aug 1, 2025
40 tasks
ferruzzi
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Aug 7, 2025
The executor_config for the Lambda executor will be plumbed through the Lambda invoke payload at the key "executor_config". We cannot use the Lambda ClientContext object because this is not supported on async Lambda invocations. When updating the docs for the Lambda executor I noticed the name was incorrect in the docs for the other AWS executors, so I've updated those as well.
fweilun
pushed a commit
to fweilun/airflow
that referenced
this pull request
Aug 11, 2025
The executor_config for the Lambda executor will be plumbed through the Lambda invoke payload at the key "executor_config". We cannot use the Lambda ClientContext object because this is not supported on async Lambda invocations. When updating the docs for the Lambda executor I noticed the name was incorrect in the docs for the other AWS executors, so I've updated those as well.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The executor_config for the Lambda executor will be plumbed through the Lambda invoke payload at the key "executor_config". We cannot use the Lambda ClientContext object because this is not supported on async Lambda invocations.
When updating the docs for the Lambda executor I noticed the name was incorrect in the docs for the other AWS executors, so I've updated as well.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.