sdg9670 opened a new issue, #55756:
URL: https://github.com/apache/airflow/issues/55756
### Apache Airflow Provider(s)
amazon
### Versions of Apache Airflow Providers
9.13.0
### Apache Airflow version
3.0.6
### Operating System
airflow docker
### Deployment
Docker-Compose
### Deployment details
_No response_
### What happened
When using the AWS Batch Executor with CloudWatch remote logging enabled,
the worker successfully calls DescribeLogGroups as shown in CloudTrail.
However, it fails to proceed with subsequent actions like CreateLogStream or
PutLogEvents, preventing logs from being sent to CloudWatch.
Worker logs
```json
{
"timestamp": "2025-09-17T07:47:47.141322Z",
"level": "warning",
"event": "Received message after logging system shutdown",
"category": "WatchtowerWarning",
"filename":
"/home/airflow/.local/lib/python3.12/site-packages/watchtower/__init__.py",
"lineno": 464,
"logger": "py.warnings"
}
```
### What you think should happen instead
_No response_
### How to reproduce
Configure the Airflow environment to use the AWSBatchExecutor.
Enable CloudWatch as the remote logging handler.
Trigger a DAG run to launch a new AWS Batch worker.
Check the CloudTrail logs for the IAM role associated with the worker.
You will observe that only the DescribeLogGroups API call is made, and no
further log-related actions are executed.
### Anything else
_No response_
### Are you willing to submit PR?
- [ ] 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]
