# AWS Glue DataBrew

AWS Glue DataBrew is a visual data preparation service for profiling, cleaning, and transforming datasets using reusable recipes.

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-glue-databrew

> DataBrew provides an interactive workspace for inspecting data samples and defining transformations without writing transformation code. Managed recipe and profile jobs apply preparation steps, generate statistics, and evaluate data quality rules for recurring analytics and machine learning workflows.

Practice exams covering AWS Glue DataBrew: [AIF-C01 AWS Certified AI Practitioner](https://blowstack.com/practice-exams/aws-certified-ai-practitioner), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate).

## 9 key features of AWS Glue DataBrew

1. **Visual preparation workspace**: Inspect a dataset sample and preview transformations in an interactive project. Choose representative sampling settings and test full-job behavior before promoting a recipe to production.
2. **Reusable, versioned recipes**: Store ordered transformation steps in recipes and publish versions for repeatable execution. Configure production jobs with the intended published version to separate development changes from scheduled processing.
3. **Managed recipe execution**: Run preparation jobs without provisioning processing servers. Configure the recipe, input, output, and processing capacity, then monitor execution status and results.
4. **Dataset profiling**: Generate dataset and column statistics to investigate missing values, cardinality, and value distributions. Use profile reports to identify issues that may not appear in the interactive sample.
5. **Data quality rulesets**: Define validation rules and evaluate them during profile jobs. For example, check that required identifiers meet a completeness threshold or that transaction amounts fall within an accepted range.
6. **Built-in transformations**: Apply supported operations for type conversion, deduplication, filtering, text normalization, joins, and aggregation. Review schema changes and record counts to detect unintended effects.
7. **Sensitive-data handling**: Use supported sensitive-data detection and transformation capabilities to identify and protect selected fields. Validate the transformed output and restrict access to raw datasets and profiling reports.
8. **Catalog-aware outputs**: Configure supported recipe-job outputs through the AWS Glue Data Catalog, including creating a new output table. For S3-only outputs, manage catalog registration separately when downstream consumers need table metadata.
9. **Scheduling and automation**: Schedule recurring jobs and manage resources through DataBrew APIs. Use workflow orchestration when downstream tasks must wait for job completion or respond to failures.

## Where AWS Glue DataBrew is used

1. **Prepare data lake datasets**: Normalize incoming files, correct column types, and write prepared output to a separate S3 location. Configure catalog output when consumers need a discoverable table, and preserve raw inputs for reprocessing.
2. **Assess incoming data quality**: Profile new sources and recurring deliveries before using them in analytics. Evaluate rules for completeness and valid ranges, and have the surrounding workflow act on validation results.
3. **Standardize reporting inputs**: Apply consistent date formats, category values, and text cleanup across recurring extracts. Publish recipe versions so reporting teams can reproduce the preparation logic used for each release.
4. **Prepare machine learning data**: Handle missing values, remove duplicates, and standardize supported fields before downstream feature engineering or training. Validate that transformations preserve labels and do not unintentionally discard important records.
5. **Prepare restricted datasets for sharing**: Transform selected sensitive fields before making prepared data available to a broader audience. Combine masking or other supported transformations with access controls on source data, outputs, and profile reports.

## How AWS Glue DataBrew is priced

- **Interactive sessions**: Interactive project usage is charged in 30-minute session units. Budget for exploration and recipe development separately from automated job execution, using the applicable regional rates.
- **Job processing**: Recipe and profile jobs are billed according to processing node usage and execution duration. Configured capacity, data volume, and transformation complexity affect total processing cost.
- **Supporting AWS services**: Additional charges can apply for S3 storage and requests, database operations, logging, encryption-key usage, and data transfer. Include prepared datasets, retained profile reports, and repeated processing in cost estimates.

## Services AWS Glue DataBrew works with

A common architecture uses Amazon S3 for raw inputs, prepared outputs, and profiling reports. DataBrew recipe jobs transform incoming files into a format and schema suitable for downstream analytics. Keep raw and prepared locations separate, and define how consumers identify the output from each successful run.

The AWS Glue Data Catalog provides table metadata for supported inputs and outputs. A recipe job can use a supported catalog output configuration, including creating a new output table, rather than requiring a separate crawler in every workflow. If the job writes only to S3, register or update metadata separately when downstream tools need a catalog table. For Redshift-sourced workflows, configure a supported connection and validate credentials, network access, and extraction permissions before scheduling recurring runs.

Use AWS Step Functions to coordinate preparation with dependent tasks and wait for successful job completion. Where data quality determines whether processing continues, include profiling and explicit evaluation of its results in the workflow. CloudWatch logs support failure investigation. Apply least-privilege IAM permissions and applicable encryption-key policies across sources, outputs, catalog resources, and reports, and keep production recipe versions separate from interactive development.

- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon S3 stores source datasets, prepared output, and profile reports for common DataBrew workflows. For example, read daily CSV deliveries from a raw-data prefix and write cleaned Parquet files to a separate prepared-data prefix. Grant the execution role the required object access and any applicable encryption-key permissions.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: DataBrew can read supported catalog tables and use supported Data Catalog output configurations for recipe jobs, including creating a new output table. For example, prepare an S3-backed sales dataset and configure the job to publish its result through a catalog table for downstream analytics. If the job instead writes only to S3, add a separate metadata-registration or crawler step when catalog-based consumers require one.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: DataBrew supports Amazon Redshift as a database source through an appropriately configured connection. For example, extract customer records from a warehouse, standardize selected fields, and write the prepared dataset to S3. Configure database credentials, network reachability, and read permissions, and account for extraction load on the warehouse.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: CloudWatch logs support troubleshooting DataBrew job execution. For example, inspect logs from a failed recipe job to determine whether the cause was inaccessible input data or a transformation error. Give the execution role the necessary logging permissions and set retention policies appropriate for operational and compliance needs.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: Step Functions provides an optimized integration that starts a DataBrew job and waits for completion. For example, run a preparation recipe before launching a downstream task that consumes the output dataset. Add retry and failure-handling paths, and grant the workflow role permission to start and monitor the job.
- **[Amazon AppFlow](https://blowstack.com/tools/cloud-services-hub/amazon-appflow)**: AWS Glue DataBrew can use data delivered by Amazon AppFlow flows as dataset inputs for profiling and recipe jobs. AppFlow is supported as a data source, not as an output destination for DataBrew recipe jobs.
- **[Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora)**: AWS Glue DataBrew can connect to Aurora MySQL and Aurora PostgreSQL tables through AWS Glue Data Catalog connections. This lets you profile and clean database data using reusable recipes.
- **[Amazon Aurora Serverless](https://blowstack.com/tools/cloud-services-hub/amazon-aurora-serverless)**: AWS Glue DataBrew can access Aurora Serverless databases through compatible MySQL or PostgreSQL connections registered in the AWS Glue Data Catalog. The connection must provide network access to the database endpoint.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: AWS Glue DataBrew uses Amazon EC2 networking APIs to create and manage network interfaces for connections to data sources in a VPC. Its service role needs the corresponding permissions to establish that connectivity.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: AWS Glue DataBrew sends job-state events to Amazon EventBridge. EventBridge rules can react to completed or failed jobs, for example by sending a notification or starting a downstream workflow.
- **[Amazon Managed Workflows for Apache Airflow (Amazon MWAA)](https://blowstack.com/tools/cloud-services-hub/amazon-managed-workflows-for-apache-airflow-(amazon-mwaa))**: AWS Glue DataBrew jobs can be orchestrated from Amazon MWAA using the Amazon provider's DataBrew operator and sensor. An Airflow workflow can start a recipe job and wait for it to finish before continuing.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: AWS Glue DataBrew can read supported Amazon RDS databases through JDBC connections or tables registered in the AWS Glue Data Catalog. Recipe jobs can also write prepared data to supported RDS database outputs.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: AWS Glue DataBrew uses configured VPC subnets and security groups to connect to private database sources. This allows preparation jobs to access databases without making their endpoints publicly accessible.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: AWS Glue DataBrew supports CloudFormation resource types for datasets, projects, recipes, jobs, schedules, and rulesets. You can provision a repeatable data-preparation setup as part of a CloudFormation stack.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: AWS Glue DataBrew API activity is recorded by AWS CloudTrail. These records let you audit actions such as creating datasets, changing recipes, and starting job runs.
- **[AWS Data Exchange](https://blowstack.com/tools/cloud-services-hub/aws-data-exchange)**: AWS Glue DataBrew can create datasets from AWS Data Exchange products that you are subscribed to or entitled to use. You can then profile and transform the third-party data with DataBrew recipes.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: AWS Glue DataBrew uses IAM policies to control access to its resources and service roles to access datasets, write outputs, and run jobs. Users need permission to pass the appropriate role when configuring projects and jobs.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: AWS Glue DataBrew supports KMS encryption for project data and job outputs. You can configure a KMS key and grant the DataBrew role permission to use it.
- **[AWS Lake Formation](https://blowstack.com/tools/cloud-services-hub/aws-lake-formation)**: AWS Glue DataBrew honors Lake Formation permissions on supported AWS Glue Data Catalog resources. Users can prepare data from those resources only when the required Lake Formation access has been granted.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: AWS Glue DataBrew supports interface VPC endpoints through AWS PrivateLink. Applications in a VPC can call the DataBrew API privately without requiring an internet gateway or NAT device.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: AWS Glue DataBrew uses Secrets Manager to store keys for deterministic encryption, decryption, and cryptographic hashing recipe steps. It also retrieves credentials from Secrets Manager for Snowflake connections.

## AWS Glue DataBrew exam questions

Real practice exam questions on AWS Glue DataBrew, with the correct answer and its explanation.

### Question 1 (AIF-C01)

**Question:**

An agricultural company is preparing crop measurements from several research partners to train a yield-prediction model. The partners use different measurement units and missing-value conventions. Before training, analysts must prepare the data without writing transformation code. A governance reviewer must also be able to verify which approved sources contributed to the training dataset and reproduce the preparation steps. Which approach best meets these requirements?

**Correct answer:** Use AWS Glue DataBrew recipes to standardize units and missing values. Retain source identifiers linked to approval records, preserve the input versions, and record the published recipe version and job configuration used for each output.

**Explanation:** DataBrew provides visual, reusable preparation steps without transformation code. Linking source identifiers to approval records supports source verification, while retaining the inputs, recipe version, and job configuration supports traceability and reproducibility.

### Question 2 (MLA-C02 (beta))

**Question:**

A logistics company receives daily shipment CSV files in Amazon S3. Analysts need a visual, no-code workflow to trim whitespace and convert a shipping_cost column from text to a numeric type. The original files must remain unchanged. Before the prepared data becomes available for ML training, the company must verify that every output record has a non-null, nonnegative shipping_cost. Invalid values are rare and might not appear in an interactive preview. A failed validation must block publication of the entire daily dataset.

Which solution meets these requirements?

**Correct answer:** Create an AWS Glue DataBrew recipe for the transformations and write its job output to a staging prefix. Run a profile job on the staged output with full-dataset sampling and a ruleset requiring 100% non-null and nonnegative shipping_cost values. Configure workflow logic to publish the output only when profiling completes and all rules pass.

**Explanation:** A recipe job performs the visual transformations without changing the source files. Profiling the complete staged output checks the actual transformed values, including rare invalid records. Explicit workflow logic that requires completed profiling and passing rules prevents failed or incomplete validation from publishing data.

### Question 3 (DEA-C01)

**Question:**

A manufacturing company stores equipment measurements in Amazon S3. Each row contains readings from 20 numeric sensors taken at the same instant. Before selecting inputs for an analytics model, a data engineer must visually identify sensor pairs with strong linear relationships, including pairs where one reading decreases as the other increases. The assessment must use the original, unaggregated measurements and must not require custom analysis code.

Which solution best meets these requirements?

**Correct answer:** Run an AWS Glue DataBrew profile job with column correlations enabled for the sensor columns. Review the column-correlation results in the console and identify pairs with correlation coefficients close to either +1 or -1.

**Explanation:** DataBrew profiling can calculate correlations between numeric columns and display the results for inspection. Coefficients close to +1 indicate strong positive linear relationships, while coefficients close to -1 indicate strong inverse linear relationships. This evaluates relationships between the original sensor measurements without custom code.

## Practice AWS Glue DataBrew in a full exam

Questions on AWS Glue DataBrew in each practice exam, with every answer option and an explanation for each:

- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 11 questions
- [MLA-C02 (beta)](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 8 questions
- [AIF-C01](https://blowstack.com/practice-exams/aws-certified-ai-practitioner): 4 questions

## What is AWS Glue DataBrew

AWS Glue DataBrew supports visual data preparation through datasets, projects, recipes, and jobs. A dataset identifies an input source and its format or connection configuration. A project provides an interactive workspace for examining a dataset sample and building transformations. A recipe records those transformations as ordered steps, while jobs execute recipes or generate data profiles independently of an interactive session.

A DataBrew dataset provides read-only access to its source data.

The project workspace operates on a sample rather than displaying every record in the source. Engineers can inspect column types, examine values, and preview operations such as type conversion, filtering, deduplication, and text normalization. Sample-based development reduces the amount of data needed for exploration, but rare values and production-scale problems may not appear in the preview. Validate recipes against representative inputs and review job results before publishing prepared data to consumers.

By default, the project sample contains the first 500 rows of the dataset.

Recipes provide a reusable definition of preparation logic. Supported operations include handling missing values, splitting and combining columns, changing formats, joining datasets, and aggregating records. Publish recipe versions and configure production jobs to use an intended version so that experimental changes do not unexpectedly alter recurring processing. Retain the input location, recipe version, and job configuration needed to reproduce important outputs.

The work-in-progress recipe is saved automatically, allowing you to leave the project and resume editing later.

Profile jobs calculate dataset and column statistics, including missing values, distinct values, and distributions. Rulesets define data quality requirements that can be evaluated during profiling, such as completeness thresholds or permitted numeric ranges. Profiling and recipe execution are separate activities: successful transformation does not by itself establish that the result meets business quality requirements. Build explicit checks and failure-handling logic into workflows that require quality gates.

DataBrew reads from Amazon S3, supported AWS Glue Data Catalog tables, and supported database connections. Recipe jobs can write prepared files to S3 and support AWS Glue Data Catalog output configurations, including creating a new output table. Choose the output configuration according to how downstream systems discover and consume the data. When using S3-only output, register or update catalog metadata separately if catalog-based consumers require it; a separate crawler is not inherently required when the job uses a supported catalog output configuration.

Operational setup includes an IAM execution role with permissions for inputs, outputs, catalog resources, logging, and applicable encryption keys. Database sources also require credentials and network connectivity. Schedule jobs for recurring preparation or orchestrate them with a workflow service when consumers must wait for successful completion. Keep raw data separate from prepared output, plan for repeated runs and output retention, and inspect execution logs when jobs fail. DataBrew fits visual, batch-oriented preparation; workloads requiring streaming execution, specialized libraries, or unsupported transformations need a different processing tool.

## Learn AWS Glue DataBrew in lessons

8 short lessons on AWS Glue DataBrew in 3 certification courses.

- AIF-C01: AWS Glue DataBrew: profiling AI datasets (Premium), https://app.blowstack.com/lessons/aws-glue-databrew-profiling-ai-datasets-aif-c01
- MLA-C02 (beta): Amazon SageMaker Data Wrangler vs AWS Glue DataBrew: choosing a visual preparation tool (Premium), https://app.blowstack.com/lessons/amazon-sagemaker-data-wrangler-vs-aws-glue-databrew-choosing-a-visual-preparation-tool-mla-c02
- DEA-C01: AWS Glue DataBrew: reusable preparation recipes (Premium), https://app.blowstack.com/lessons/aws-glue-databrew-reusable-preparation-recipes-dea-c01
- MLA-C02 (beta): AWS Glue DataBrew: reusable preparation recipes (Premium), https://app.blowstack.com/lessons/aws-glue-databrew-reusable-preparation-recipes-mla-c02
- DEA-C01: AWS Glue DataBrew: profile-based data quality (Premium), https://app.blowstack.com/lessons/aws-glue-databrew-profile-based-data-quality-dea-c01
- MLA-C02 (beta): AWS Glue DataBrew: profiles and quality rulesets (Premium), https://app.blowstack.com/lessons/aws-glue-databrew-profiles-and-quality-rulesets-mla-c02

## Concepts related to AWS Glue DataBrew

- [Data Profiling](https://blowstack.com/tools/cloud-concepts-hub/data-profiling): Data profiling is the systematic examination of a dataset’s structure, values, distributions, and relationships to understand its characteristics and identify potential quality problems.
- [Referential Integrity](https://blowstack.com/tools/cloud-concepts-hub/referential-integrity): Referential integrity ensures that references between related records point to existing, valid target records.
- [Schema Validation](https://blowstack.com/tools/cloud-concepts-hub/schema-validation): Schema validation checks whether data conforms to an explicitly defined structure, including required fields, data types, and permitted values.
- [Uniqueness Constraints](https://blowstack.com/tools/cloud-concepts-hub/uniqueness-constraints): Uniqueness constraints are rules that require a column value or combination of column values to occur no more than once within a defined scope.
