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

   ### Apache Airflow version
   
   3.1.2
   
   ### If "Other Airflow 2/3 version" selected, which one?
   
   3.1.1
   
   ### What happened?
   
   I have created an AWS connection which can connect to an S3 bucket for 
remote logging, let's say the connection ID is "s3_conn_logs".  When the worker 
started, I can see it fetched the credentials via task SDK API calls to the 
execution API interface and it's a 200 OK in API log, but after the task 
completed it failed with error message below:
   Unable to retrieve connection from secret 
backend(EnvironmentVariablesBackend). Checking subsequent secrets backend.
   Unable to find AWS Connection ID 's3_conn_logs', switching to empty.
   No connection ID provided, Fallback on boto3 credential strategy.
   
   ### What you think should happen instead?
   
   Since worker already has successfully fetched the credential for S3, it 
should be able to use it and upload the logs to S3.
   
   ### How to reproduce
   
   1. create an AWS connection in the Airflow UI( the connection can be a dummy 
one), let's say the ID is s3_conn_logs
   2. enable the task remote logging by adding these configurations into 
airflow.cfg config map:
       remote_base_log_folder = s3://your_bucket_name
       remote_log_conn_id = s3_conn_logs
       remote_logging = True
   3. manual trigger any DAG
   
   ### Operating System
   
   Debian
   
   ### Versions of Apache Airflow Providers
   
   I'm using the default version in 3.1.2
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   normal deployment
   
   ### 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]

Reply via email to