From 1367f0216575d8cb397ea6560cd285ce782bf7a2 Mon Sep 17 00:00:00 2001
From: Pavan Nandi <93924999+pavansai1997@users.noreply.github.com>
Date: Wed, 4 Nov 2026 02:37:04 +0530
Subject: [PATCH] Fix env var names in AWS ECS and Lambda executor setup docs
 (#76155)

The AWS console setup steps told users to set AIRFLOW__ECS_EXECUTOR__*
and AIRFLOW__LAMBDA_EXECUTOR__* variables, but the executors read the
aws_ecs_executor and aws_lambda_executor config sections. Airflow
silently ignored the documented variables, so ECS tasks started without
the security groups and subnets needed to reach the metadata database,
and the Lambda executor had no SQS queue URL.
---
 providers/amazon/docs/executors/ecs-executor.rst    | 4 ++--
 providers/amazon/docs/executors/lambda-executor.rst | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/providers/amazon/docs/executors/ecs-executor.rst b/providers/amazon/docs/executors/ecs-executor.rst
index 67d3f2165b1..573c164a933 100644
--- a/providers/amazon/docs/executors/ecs-executor.rst
+++ b/providers/amazon/docs/executors/ecs-executor.rst
@@ -339,9 +339,9 @@ Create Task Definition
   :end-before: .. END SQL_ALCHEMY_CONN
 
 
-- ``AIRFLOW__ECS_EXECUTOR__SECURITY_GROUPS``, with the value being a comma separated list of security group IDs associated with the VPC used for the RDS instance.
+- ``AIRFLOW__AWS_ECS_EXECUTOR__SECURITY_GROUPS``, with the value being a comma separated list of security group IDs associated with the VPC used for the RDS instance.
 
-- ``AIRFLOW__ECS_EXECUTOR__SUBNETS``, with the value being a comma separated list of subnet IDs of the subnets associated with the RDS instance.
+- ``AIRFLOW__AWS_ECS_EXECUTOR__SUBNETS``, with the value being a comma separated list of subnet IDs of the subnets associated with the RDS instance.
 
 1. Add other configuration as necessary for Airflow generally (see `here <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html>`__), the ECS executor (see :ref:`here <config-options>`) or for remote logging (see :ref:`here <logging>`). Note that any configuration changes should be made across the entire Airflow environment to keep configuration consistent.
 
diff --git a/providers/amazon/docs/executors/lambda-executor.rst b/providers/amazon/docs/executors/lambda-executor.rst
index 123501e8915..0e26e775809 100644
--- a/providers/amazon/docs/executors/lambda-executor.rst
+++ b/providers/amazon/docs/executors/lambda-executor.rst
@@ -357,7 +357,7 @@ Finally create the function:
   :end-before: .. END SQL_ALCHEMY_CONN
 
 
-- ``AIRFLOW__LAMBDA_EXECUTOR__QUEUE_URL``, with the value being the URL of the SQS queue created above.
+- ``AIRFLOW__AWS_LAMBDA_EXECUTOR__QUEUE_URL``, with the value being the URL of the SQS queue created above.
 
 7. Add other configuration as necessary for Airflow generally (see `here <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html>`__), the Lambda executor (see :ref:`here <lambda_config-options>`) or for remote logging (see :ref:`here <lamba_logging>`). Note that any configuration changes should be made across the entire Airflow environment to keep configuration consistent.