ReadytoRocc opened a new issue, #25326: URL: https://github.com/apache/airflow/issues/25326
### Description My current understanding, is that the methods documented [here](https://docs.aws.amazon.com/cli/latest/topic/config-vars.html#credentials) outline the ways we can authorize AWS Secrets Manager or AWS Systems Manager as a [Secrets Backend](https://airflow.apache.org/docs/apache-airflow/2.3.3/security/secrets/secrets-backend/index.html). This does not include the Assume Role methods offered in the **[AWSBaseHook](https://github.com/apache/airflow/blob/main/airflow/providers/amazon/aws/hooks/base_aws.py#L609)**. I am prosing we extend the Secrets Backend integrations, so that they can use Assume Role methods to connect to these services. ### Use case/motivation This would enable different authorization methods when connecting to AWS Secrets Backends. This could reduce the number of cases where users need to deploy Access & Secret Keys to their Airflow environment. On K8s for example example, users could use the Role of the Worker or Scheduler Pod (once authorized) to connect to the service powering their Secrets Backend. ### Related issues _No response_ ### Are you willing to submit a PR? - [X] 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]
