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

   ### Apache Airflow Provider(s)
   
   amazon
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Apache Airflow version
   
   3.0.2
   
   ### Operating System
   
   ebian GNU/Linux 12 (bookworm)
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   Airflow verison: 3.0.2
   Provider version: 9.9.0
   Executor: AWS Batch
   Permissions: Handled by the IAM role attached to the EC2 instances in the 
compute environment.
   
   ### What happened
   
   The task running on AWS Batch is not writing any logs to Amazon CloudWatch. 
It completes successfully without leaving any specific error messages or logs.
   
   ## Logs about amazon
   ```
   [2025-06-27T04:55:46.050+0000] {base_aws.py:623} WARNING - Unable to find 
AWS Connection ID 'aws_default', switching to empty.
   --
   [2025-06-27T04:55:46.051+0000] {base_aws.py:189} INFO - No connection ID 
provided. Fallback on boto3 credential strategy (region_name='ap-northeast-2'). 
See: 
https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html
   --
   {
       "timestamp": "2025-06-27T04:56:20.255576",
       "level": "info",
       "event": "No connection ID provided. Fallback on boto3 credential 
strategy (region_name=None). See: 
https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html";,
       "logger": 
"airflow.providers.amazon.aws.hooks.base_aws.BaseSessionFactory"
   }
   ```
   
   ### What you think should happen instead
   
   _No response_
   
   ### How to reproduce
   
   We are using Apache Airflow with the AWSBatchExecutor to schedule and submit 
our worker tasks to AWS Batch.
   
   
   ## AWS batch service role
   ```json
   {
       "Effect": "Allow",
       "Action": [
           "logs:CreateLogGroup",
           "logs:CreateLogStream",
           "logs:PutLogEvents"
       ],
       "Resource": "*"
   }
   ```
   
   ## Worker Configuration
   ```bash
   ENV AIRFLOW__LOGGING__REMOTE_LOGGING='true'
   ENV 
AIRFLOW__LOGGING__REMOTE_BASE_LOG_FOLDER="cloudwatch://${AWS_CLOUDWATCH_GROUP_ARN}"
   ENV AIRFLOW__LOGGING__REMOTE_LOG_CONN_ID='aws_default'
   ```
   
   ### Anything else
   
   This configuration was working correctly in Airflow 2, but logging to 
CloudWatch stopped after we upgraded to Airflow 3.
   
   ### 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]

Reply via email to