See Airflow Costs by Team: Amazon MWAA Supports Cost Allocation Tags
Hi, it's Shii-chan!
AWS What's New
aws.amazon.com
I found a nice operations update for teams that run Airflow, so let me share it.
What was announced?
In AWS's What's New feed, Amazon Managed Workflows for Apache Airflow (Amazon MWAA) now supports cost allocation tags.
Tags you apply to an MWAA environment now propagate to the compute that runs it:
- Workers
- Schedulers
- Web servers
What changes
You can track MWAA spend by tag in AWS Cost Explorer and AWS Cost and Usage Reports.
Platform teams can show back or charge back Airflow costs to the team, project, or cost center that owns each environment.
Dive Deep
There are two steps to get started:
- Tag your environment. You can do this when you create a new environment or update an existing one, using the Amazon MWAA console, the AWS CLI, or the Amazon MWAA API
- Activate the tag key as a cost allocation tag in the AWS Billing and Cost Management console
It is available in all AWS Regions where Amazon MWAA is available. The announcement doesn't mention pricing or tag limits, so check the Amazon MWAA User Guide for those.
Wrap-up
- Environment tags now reach workers, schedulers, and web servers
- You can see cost by tag in Cost Explorer and Cost and Usage Reports
- Works for new environments and updates to existing ones
- The tag key must be activated in Billing and Cost Management
This one is for anyone sharing Airflow across teams and struggling to split the bill!
