nwsparks opened a new issue, #35164: URL: https://github.com/apache/airflow/issues/35164
### Description Please add an option to disable attempting to create the cloudwatch log group when remote logging is enabled or just disable the behavior and require the the group already exists. ### Use case/motivation We have enabled remote logging to CloudWatch. After doing so, we see that some of our dags with a lot of parallelization are hitting this error and then never executing: `stderr F botocore.exceptions.ClientError: An error occurred (ThrottlingException) when calling the CreateLogGroup operation (reached max retries: 4): Rate exceeded` I am guessing that on the launch of each task, it is trying to create the log group defined here https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#remote-base-log-folder This is unnecessary if the log group was already created. ### Related issues _No response_ ### Are you willing to submit a 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: commits-unsubscr...@airflow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
