geocomm-descue commented on issue #57356: URL: https://github.com/apache/airflow/issues/57356#issuecomment-3507482700
>However if I change `remote_log_conn_id: "aws_default"` to `remote_log_conn_id: "aws"` the errors goes away and the logs >correctly end up both in the UI and Cloudwatch (after creating the connection) Just to clarify, are you creating a connection and populating it in the airflow UI? We're seeing the error when the connection isn't populated since we want to be using IAM roles provided to the pods. These are the docs we've been working off of. https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/connections/aws.html If you are indeed populating the connection, then maybe this is an error in the fallback to boto3 credentialing logic? -- 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]
