Pavan Nandi 1367f02165 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.

2026-11-03 14:07:04 -07:00

..

batch-executor.rst

Carry task attempt UUIDs through remote executor providers (#73917)

2026-10-03 09:02:17 +01:00

ecs-executor.rst

Fix env var names in AWS ECS and Lambda executor setup docs (#76155)

2026-11-03 14:07:04 -07:00

eks-executor.rst

Let the EKS executor run per team and next to KubernetesExecutor (#75449)

2026-10-26 17:12:02 -04:00

general.rst

Add AwsEksExecutor to the Amazon provider (#74399)

2026-10-19 18:02:34 -07:00

index.rst

Add AwsEksExecutor to the Amazon provider (#74399)

2026-10-19 18:02:34 -07:00

lambda-executor.rst

Fix env var names in AWS ECS and Lambda executor setup docs (#76155)

2026-11-03 14:07:04 -07:00