# Amazon Managed Workflows for Apache Airflow (Amazon MWAA)

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/amazon-managed-workflows-for-apache-airflow-(amazon-mwaa)

> Amazon Managed Workflows for Apache Airflow (Amazon MWAA) is a cloud service that orchestrates complex data workflows, allowing users to manage, execute, and scale Apache Airflow environments on the AWS cloud without managing the underlying infrastructure.

Practice exams covering Amazon Managed Workflows for Apache Airflow (Amazon MWAA): [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate).

## 6 key features of Amazon Managed Workflows for Apache Airflow (Amazon MWAA)

Amazon MWAA offers scalable serverless workflow management, easy integration with AWS services, built-in security features, swift deployment options, and comprehensive monitoring and logging capabilities.

1. **Serverless Workflow Management**: Amazon MWAA automatically scales the workflow execution capacity to match your workload without requiring manual server management, ensuring efficient resource utilization.
2. **Integrated with AWS Services**: Seamlessly integrates with various AWS services such as AWS Lambda, Amazon S3, Amazon ECS, and Amazon RDS, enabling a more efficient and smooth operation of data pipelines.
3. **Built-in Security**: Provides built-in features such as encryption in transit and at rest, enabling you to secure your data workflows without additional configuration.
4. **Easy Deployment**: Offers simple and quick deployment options for your Apache Airflow environment, allowing you to get your data pipelines up and running rapidly.
5. **Monitoring and Logging**: Amazon MWAA integrates with Amazon CloudWatch and Amazon CloudTrail for extensive monitoring and logging, giving you full visibility into your Apache Airflow workflows.
6. **Public or Private Airflow UI Access**: Provisioned environments support private or public network access to the Apache Airflow web UI, with user access controlled by IAM policies in either configuration.

## Where Amazon Managed Workflows for Apache Airflow (Amazon MWAA) is used

Amazon Managed Workflows for Apache Airflow (Amazon MWAA) is principally used for orchestrating complex data pipelines, automating machine learning model training, executing ETL jobs, and managing batch processing tasks, streamlining these operations with efficient task management and scheduling.

1. **Data Pipeline Orchestration**: Amazon MWAA facilitates the scheduling and orchestration of complex data pipelines. Users can easily manage the execution of multiple data processing tasks in a specific sequence or in parallel, ensuring that dependencies are managed and that the workflow is executed efficiently.
2. **Machine Learning Model Training**: Amazon MWAA can be used to automate the training of machine learning models by orchestrating various steps involved in the process, such as data preprocessing, model training, model evaluation, and model deployment, ensuring that each step is executed once the prerequisites are met.
3. **ETL Jobs**: Amazon MWAA simplifies the execution of Extract, Transform, Load (ETL) jobs by managing the dependencies and execution order of tasks. It allows for efficient processing and transformation of large volumes of data from various sources before loading it into a data warehouse or data lake.
4. **Batch Processing**: This use case involves leveraging Amazon MWAA to manage and execute batch processing jobs, which can include tasks such as data analysis, computation, and the execution of scripts. Amazon MWAA ensures these jobs are run on a schedule or in response to specific triggers.

## How Amazon Managed Workflows for Apache Airflow (Amazon MWAA) is priced

Amazon MWAA pricing includes a fixed monthly charge per environment plus variable charges based on the vCPU and memory resources used by your workflows, with overall costs affected by the region.

- **Environment Pricing**: Provisioned environments are charged hourly, billed at one-second resolution, with rates that vary by environment size.
- **Serverless Task Pricing**: MWAA Serverless charges for AWS Managed Tasks and Customer Managed Tasks by task duration, at hourly rates billed at one-second resolution with a one-minute minimum.
- **Additional Worker Instance Pricing**: Additional worker instances used for auto-scaling are charged hourly at one-second resolution, with rates that vary by environment size.
- **Additional Scheduler Instance Pricing**: Scheduler instances beyond those included with the environment incur additional hourly instance charges.
- **Additional Web Server Instance Pricing**: Additional web server instances are charged for the duration the environment is available, at hourly rates billed at one-second resolution that vary by environment size.
- **Metadata Database Storage**: Metadata database storage is charged per GB-month based on storage consumed, without advance provisioning.

## Services Amazon Managed Workflows for Apache Airflow (Amazon MWAA) works with

- **[Amazon AppFlow](https://blowstack.com/tools/cloud-services-hub/amazon-appflow)**: Amazon MWAA workflows can use Apache Airflow's AppFlow operators to start flows and monitor their completion. This lets a workflow wait for SaaS data ingestion before starting downstream processing.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: Amazon MWAA can submit Athena queries and wait for their results using dedicated Airflow operators and sensors. Workflows can use these queries to transform or validate data stored in Amazon S3.
- **[Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora)**: Amazon MWAA uses an AWS-managed Aurora PostgreSQL database for Apache Airflow metadata. AWS provisions and operates this database as part of the environment.
- **[Amazon Bedrock](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock)**: Amazon MWAA workflows can use dedicated Bedrock operators to invoke models and orchestrate supported model customization and batch inference jobs. Sensors can wait for asynchronous jobs before downstream tasks consume their results.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Amazon MWAA publishes environment metrics and configurable Airflow logs to CloudWatch. You can monitor scheduler and worker health, inspect task failures, and create alarms for operational problems.
- **[Amazon Comprehend](https://blowstack.com/tools/cloud-services-hub/amazon-comprehend)**: Amazon MWAA can orchestrate Comprehend analysis jobs through dedicated Airflow operators. A workflow can submit documents for entity recognition and wait for the analysis before processing the output.
- **[Amazon DataZone](https://blowstack.com/tools/cloud-services-hub/amazon-datazone)**: Amazon MWAA can publish workflow lineage to Amazon DataZone using an Airflow OpenLineage integration. This connects Airflow job executions with their input and output datasets in the data catalog.
- **[Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb)**: Amazon MWAA workflows can use DynamoDB-specific Airflow hooks, sensors, and transfer operators. For example, a workflow can wait for table availability or export table records to Amazon S3 for downstream processing.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon MWAA can use dedicated EC2 operators and sensors to create, start, stop, terminate, and monitor instances. This allows workflows to coordinate instance-based processing with other pipeline tasks.
- **[Amazon Elastic Container Registry (Amazon ECR)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr))**: Amazon MWAA workflows can use Airflow's ECR hook to obtain registry authorization credentials. These credentials can authenticate container workloads launched by a workflow against private ECR repositories.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: Amazon MWAA can launch ECS tasks and monitor their completion using dedicated Airflow operators. A workflow can run a containerized transformation and continue only after the task succeeds.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: Amazon MWAA can orchestrate workloads on EKS using Airflow's Kubernetes and EKS operators. Workflows can launch pods for processing tasks and manage EKS cluster and node group lifecycles.
- **[Amazon ElastiCache](https://blowstack.com/tools/cloud-services-hub/amazon-elasticache)**: Amazon MWAA workflows can use Airflow's ElastiCache hook to work with cache snapshots, including copying snapshot data to Amazon S3. This can incorporate cache exports into scheduled data workflows.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: Amazon MWAA can create EMR clusters, submit processing steps, and monitor their execution through dedicated operators and sensors. It also supports orchestration of EMR Serverless jobs and EMR on EKS job runs.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: Amazon MWAA workflows can publish custom events to EventBridge using Airflow's EventBridge operator. A successful processing task can emit an event that starts downstream event-driven processing.
- **[Amazon Kinesis Data Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-streams)**: Amazon MWAA workflows can use Airflow's Kinesis hook to write records to Kinesis Data Streams. This lets a scheduled workflow publish processed records into a streaming pipeline.
- **[Amazon Managed Streaming for Apache Kafka](https://blowstack.com/tools/cloud-services-hub/amazon-managed-streaming-for-apache-kafka)**: Amazon MWAA can use Airflow's MSK integration to retrieve cluster connection information and orchestrate supported cluster operations. Airflow's Kafka operators and sensors can then produce or consume records through the cluster's Kafka endpoints.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: Amazon MWAA can run Airflow's OpenSearch operators and hooks to execute searches and indexing operations against OpenSearch Service domains. A workflow can index newly processed documents or query an index to validate a data load.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: Amazon MWAA can start QuickSight dataset ingestions and monitor their completion using dedicated Airflow operators and sensors. This lets a workflow refresh a SPICE dataset after its underlying data has been updated.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Amazon MWAA workflows can orchestrate RDS snapshot creation, copying, deletion, and snapshot exports using dedicated Airflow operators. Sensors can wait for snapshots and export tasks before subsequent processing begins.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: Amazon MWAA can execute Redshift SQL, manage clusters, and move data between Redshift and Amazon S3 through dedicated Airflow integrations. A workflow can load staged data, run transformations, and validate the resulting warehouse tables.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon MWAA loads workflow definitions, plugins, Python requirements, and optional startup scripts from an S3 bucket. Workflows can also use S3 operators and sensors to detect arriving objects, transfer data, and manage stored files.
- **[Amazon S3 Glacier](https://blowstack.com/tools/cloud-services-hub/amazon-s3-glacier)**: Amazon MWAA workflows can use Airflow's Glacier integration to initiate archive retrieval jobs and obtain their output. This allows retrieval from Glacier vaults to be coordinated with subsequent data processing.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: Amazon MWAA can orchestrate SageMaker training, processing, tuning, batch transform, model deployment, and pipeline executions through dedicated Airflow operators. Sensors can wait for machine learning jobs before evaluation or deployment tasks proceed.
- **[Amazon Simple Email Service (Amazon SES)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-email-service-(amazon-ses))**: Amazon MWAA can use Airflow's SES email backend or hook to send workflow notifications. For example, a DAG can email an operational summary or notify maintainers when a task fails.
- **[Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns))**: Amazon MWAA workflows can publish messages to SNS topics using a dedicated Airflow operator. This can notify subscribers when a pipeline finishes or encounters a failure.
- **[Amazon Simple Queue Service (Amazon SQS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-queue-service-(amazon-sqs))**: Amazon MWAA uses SQS as the queue for distributing work to its Airflow workers. Workflows can also use SQS operators and sensors to send messages or wait for incoming messages.
- **[Amazon Textract](https://blowstack.com/tools/cloud-services-hub/amazon-textract)**: Amazon MWAA can start Textract document-processing jobs and coordinate their results using dedicated Airflow operators. A workflow can extract text or structured information from documents before loading it into an analytics system.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon MWAA connects its schedulers and workers to private subnets in your VPC. Subnet routing and security groups control access to databases, service endpoints, and other resources used by workflows.
- **[AWS Batch](https://blowstack.com/tools/cloud-services-hub/aws-batch)**: Amazon MWAA can submit AWS Batch jobs and monitor their execution through dedicated Airflow operators and sensors. This allows compute-intensive batch processing to run as a managed step in a larger workflow.
- **[AWS Clean Rooms](https://blowstack.com/tools/cloud-services-hub/aws-clean-rooms)**: Amazon MWAA can use dedicated Airflow operators to start Clean Rooms protected queries and wait for their completion. This lets collaborative analysis become a scheduled step in a data pipeline.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: Amazon MWAA environments can be provisioned and updated through CloudFormation using the AWS::MWAA::Environment resource type. MWAA workflows can also use Airflow's CloudFormation operators to create or delete stacks and wait for stack operations.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Amazon MWAA management API calls are recorded by CloudTrail. These records support auditing actions such as creating, updating, and deleting environments.
- **[AWS CodeBuild](https://blowstack.com/tools/cloud-services-hub/aws-codebuild)**: Amazon MWAA workflows can start CodeBuild builds and monitor their status through Airflow's CodeBuild integration. A pipeline can build or test an artifact before using it in subsequent processing.
- **[AWS CodePipeline](https://blowstack.com/tools/cloud-services-hub/aws-codepipeline)**: Amazon MWAA can use Airflow's CodePipeline hook and sensors to coordinate with pipeline executions and wait for pipeline or stage completion. This allows a workflow to depend on a successful software delivery stage.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config can record configuration changes to Amazon MWAA environments. The recorded resource history can be used to assess environment configuration and investigate changes.
- **[AWS Database Migration Service (AWS DMS)](https://blowstack.com/tools/cloud-services-hub/aws-database-migration-service-(aws-dms))**: Amazon MWAA can create, start, stop, and monitor DMS replication tasks using dedicated Airflow operators and sensors. A workflow can coordinate a database migration or replication stage with downstream validation.
- **[AWS DataSync](https://blowstack.com/tools/cloud-services-hub/aws-datasync)**: Amazon MWAA can launch DataSync task executions and wait for transfers to finish using a dedicated Airflow operator. Downstream processing can begin only after the required files have reached their destination.
- **[AWS Fargate](https://blowstack.com/tools/cloud-services-hub/aws-fargate)**: Amazon MWAA provisions and operates Fargate compute for its Airflow schedulers, workers, and webservers. Workflows can also launch their own Fargate tasks through Airflow's ECS integration.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: Amazon MWAA can start Glue jobs and crawlers, monitor their completion, and coordinate Glue Data Catalog partitions. Workflows can also orchestrate Glue Data Quality runs before allowing data to move to later stages.
- **[AWS Glue DataBrew](https://blowstack.com/tools/cloud-services-hub/aws-glue-databrew)**: Amazon MWAA workflows can start DataBrew jobs using a dedicated Airflow operator and wait for their completion. This lets recipe-based data preparation run as part of a scheduled pipeline.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Amazon MWAA uses an IAM execution role to access workflow files, logs, queues, and services called by Airflow tasks. IAM policies also control who can manage environments and obtain access to the Airflow interface.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: Amazon MWAA supports customer-managed KMS keys for encrypting environment data, including its metadata database and associated managed resources. The environment's execution role and key policy must permit the required cryptographic operations.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: Amazon MWAA can invoke Lambda functions and wait for function readiness using dedicated Airflow operators and sensors. A workflow can delegate a short processing or validation task to a function.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: Amazon MWAA supports interface VPC endpoints powered by PrivateLink for private access to supported MWAA API and environment endpoints. This allows access without routing traffic over the public internet.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: Amazon MWAA can use Secrets Manager as an Apache Airflow secrets backend for connections and variables. Workflow tasks can retrieve database credentials without embedding them in DAG files.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: Amazon MWAA workflows can use Airflow AWS connections configured to assume IAM roles through STS. This supplies temporary credentials for tasks that access resources in another account or require a separate role.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: Amazon MWAA can start Step Functions state machine executions and monitor their completion using dedicated Airflow operators and sensors. This lets an Airflow DAG coordinate a state machine as one stage of a larger workflow.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: Amazon MWAA can use Systems Manager Parameter Store as an Airflow secrets backend. Connections and variables can be retrieved from parameters instead of being stored directly in Airflow's metadata database.

## What is Amazon Managed Workflows for Apache Airflow (Amazon MWAA)

Amazon Managed Workflows for Apache Airflow (Amazon MWAA) is a cloud service provided by Amazon Web Services (AWS) designed to simplify running Apache Airflow on the AWS cloud. Apache Airflow is an open-source platform used for orchestrating complex computational workflows and data processing pipelines. By leveraging Amazon MWAA, users can take advantage of Apache Airflowâs powerful capabilities without the complexity of setting up, configuring, and managing the environment themselves. This managed service automates tasks such as provisioning resources, scaling according to the workload, and monitoring the health of instances. Amazon MWAA builds and patches version images, but an environment continues using its specified image version until you explicitly update the environment to a later version.

Amazon MWAA offers serverless and provisioned deployment options. Amazon MWAA Serverless automatically executes YAML or Python-based workflows on demand or on a schedule, without requiring Apache Airflow configuration.

Amazon MWAA Serverless has a maximum task execution timeout of 60 minutes.

The default Amazon MWAA Serverless concurrent-run quotas are 100 runs per account and 20 runs per workflow in each AWS Region.

One of the key benefits of using Amazon MWAA is its deep integration with other AWS services. This allows users to easily create workflows that utilize AWS services such as Amazon S3 for storage, Amazon Redshift for data warehousing, AWS Lambda for serverless compute, and many others without extensive configuration. The integration is designed to be seamless, enabling users to directly reference AWS resources within their Airflow DAGs (Directed Acyclic Graphs), which are the collection of tasks you want to run, organized to reflect their relationships and dependencies.

Amazon MWAA follows best practices for high availability and security. For provisioned environments, Amazon MWAA creates an AWS-owned VPC hosting the webserver and metadata database; the scheduler and workers connect to private subnets in the VPC that you own and configure. The service is built to scale, so as the demand for processing increases, Amazon MWAA can automatically adjust resources to meet the workload demands without the need for manual intervention. Security in Amazon MWAA is a top priority, and the service offers features such as encryption in transit and at rest, integration with AWS Identity and Access Management (IAM) for fine-grained access control, and logging through Amazon CloudWatch. These capabilities ensure that user data is protected and that administrators can audit and monitor access and usage.

Provisioned environments can be configured with up to 25 workers through the console; a quota increase can allow up to 50 workers.

Provisioned worker autoscaling operates between configured minimum and maximum worker counts. It scales out when queued and running tasks exceed existing worker capacity, and scales back to the minimum when the combined number of queued and running tasks remains zero for more than two minutes.

Getting started with Amazon MWAA is straightforward. Users can set up their Airflow environment through the AWS Management Console, via the AWS Command Line Interface (CLI), or using Infrastructure as Code tools such as AWS CloudFormation. This flexibility allows users to integrate Amazon MWAA into their existing CI/CD pipelines and infrastructure management practices easily.

In conclusion, Amazon Managed Workflows for Apache Airflow simplifies the deployment, management, and scalability of Apache Airflow environments on AWS. It enables data engineers and developers to focus on designing workflows and writing DAGs rather than managing infrastructure. With its robust integration with AWS services, high availability, security features, and flexible deployment options, Amazon MWAA is a powerful tool for automating and orchestrating complex data processing tasks in the cloud.
