- Newest
- Most votes
- Most comments
You can control the Secrets Manager API call by MWAA by having "connections_lookup_pattern" with "secrets.backend_kwargs" configuration.
Configuring an Apache Airflow connection using a AWS Secrets Manager secret - Step two: Create the Secrets Manager backend as an Apache Airflow configuration option - https://docs.aws.amazon.com/mwaa/latest/userguide/connections-secrets-manager.html#connections-sm-aa-configuration
Note if you are using the 7.3 provider version and you are on private you will need to update it in your plugins.zip. Do not follow instructions that tell you to put a constraints.txt in you dags folder it will not upload and will crash your EVN.
Every time a boto session is created many log lines are added regarding how the session was
constructed. Looks like change has been pushed to change the logging to debug . please find
https://github.com/apache/airflow/pull/20858
I saw that, but my issue isn't necessarily with it spamming the logs, but making millions of calls to Secrets Manager per month. I'd like to be able to point it somewhere else when creating a boto session (especially since it's not actually using the credentials from Secrets Manager to do create that Session).
Relevant content
- asked a year ago
- asked 3 years ago
- asked a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 months ago
Were you able to every find a solution to this issue? I would like to not spend $20 a month on bogus api calls.