Add options to push Airflow Audit Logs to CloudWatch
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 472
Description
### Description
Audit Logs are only visible in the GUI under Admin. For all audit related reasons, these logs have to be available on cloudwatch to be integrated with Splunk.
### Use case/motivation
Airflow can have an configuration option to push these audit logs to Cloudwatch. As of now they are accessible through the eventLogs API. All usage going to production, should write an external Lambda to call the API to push the logs to cloudwatch for monitoring.
### 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)
Contributor guide
Research direction
Start by reviewing Airflow's eventLogs API and the audit logs exposed under the Admin GUI, then examine how CloudWatch integrations and configuration options are handled. Done means production audit logs can be pushed to CloudWatch without requiring an external Lambda to consume the API, with the resulting logs available for Splunk monitoring.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- backend, cloud, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100