# Amazon DataZone

Amazon DataZone is a data management service for cataloging, discovering, sharing, and governing access to data across organizational boundaries.

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

> Amazon DataZone provides a business data catalog and workflows that connect data producers with consumers through projects, metadata, and access subscriptions. It integrates with AWS analytics and governance services so teams can publish discoverable data assets and provision approved access without moving the underlying data into the catalog.

Practice exams covering Amazon DataZone: [AIB-C01 (beta) AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate).

## 10 key features of Amazon DataZone

1. **Business data catalog**: Publish searchable data assets with technical schemas, ownership information, and business descriptions. Consumers can evaluate an asset before requesting access instead of relying on direct conversations with its producer.
2. **Business glossaries and metadata forms**: Define shared terminology and structured metadata fields for assets. Use glossary terms for consistent business concepts and forms for information such as stewardship, sensitivity classification, or refresh expectations.
3. **Projects and analytics environments**: Organize collaborators into projects and provision environments through administrator-configured blueprints and profiles. This gives teams a controlled way to obtain the resources and roles needed to publish and consume data.
4. **Metadata ingestion and publishing**: Import metadata from supported sources such as the AWS Glue Data Catalog and Amazon Redshift. Producers can curate assets in project inventory before publishing them for broader discovery.
5. **Subscription approval and fulfillment**: Route access requests to authorized approvers and track subscription decisions. Supported integrations can provision underlying permissions, while other assets require custom or external fulfillment.
6. **Domain units and delegated governance**: Use domain units to structure ownership and administration within a domain. Delegate selected responsibilities to business or technical teams while retaining domain-level controls.
7. **Data lineage**: Capture and visualize lineage supplied through supported integrations and lineage APIs, including OpenLineage-compatible events. Use it to investigate upstream dependencies and assess the likely impact of changes.
8. **Data quality visibility**: Expose supported data quality results alongside catalog assets. Consumers can review available quality signals, but producers must still configure and operate the checks that generate them.
9. **AI-assisted business descriptions**: Generate recommended business metadata for supported assets to reduce manual documentation work. Producers should review generated descriptions for accuracy before publishing them.
10. **Cross-Region data sharing**: Share and access data across supported AWS Regions.

## Where Amazon DataZone is used

1. **Cross-team analytics data sharing**: Publish curated datasets from producer teams and let analysts request access through a consistent subscription workflow. Keep data in its existing storage or warehouse while granting access through supported integrations.
2. **Business-oriented data discovery**: Attach glossary terms, ownership details, and business descriptions to technical tables. Analysts can search for concepts such as net revenue or active customers without first knowing database and table names.
3. **Distributed data ownership**: Allow business units to curate and approve access to their own data products while platform teams manage shared domain configuration and environment provisioning.
4. **Governed cross-account consumption**: Associate participating AWS accounts with a domain and configure supported environments for producers and consumers. Validate IAM, Lake Formation, resource policies, and encryption permissions as part of onboarding.
5. **Data suitability and impact assessment**: Use published metadata, quality results, and lineage to evaluate a dataset before adopting it. Review downstream dependencies before changing schemas or retiring upstream assets.

## How Amazon DataZone is priced

- **Metadata storage**: Usage-based charges apply to metadata stored in the service. Catalog size, metadata enrichment, and retained lineage information can affect consumption; underlying dataset storage is billed separately by its storage service.
- **API requests**: API usage is metered under DataZone pricing. Automated catalog synchronization, frequent searches, and custom workflow integrations should be included in request-volume estimates.
- **Compute usage**: DataZone meters compute used for applicable service processing activities. Consider metadata ingestion frequency and processing volume when estimating usage.
- **AI-generated recommendations**: Business description generation has usage-based pricing for the AI recommendation capability. Review its current pricing dimensions before enabling generation across large catalogs.
- **Associated AWS resource charges**: Storage, queries, data processing, and infrastructure used by project environments are billed by their respective AWS services. DataZone charges do not include services such as Amazon S3, Amazon Athena, AWS Glue, or Amazon Redshift.

## Services Amazon DataZone works with

A common data lake architecture uses the AWS Glue Data Catalog for technical table definitions, Amazon DataZone for business discovery and subscriptions, AWS Lake Formation for governed permissions, and Amazon Athena for queries. Producers ingest metadata into project inventory, enrich it, and publish assets. After approval, supported subscription fulfillment grants access to the consumer environment without copying the underlying dataset.

Warehouse-oriented deployments connect DataZone to Amazon Redshift so teams can discover and request access to warehouse assets through the same catalog experience. Keep database connectivity, account associations, environment roles, and encryption permissions aligned with the chosen deployment. Catalog visibility and effective query access are separate controls and should be tested independently.

IAM Identity Center commonly provides workforce portal access, while project membership and environment configuration determine how users collaborate and reach analytics resources. EventBridge can connect subscription events to custom fulfillment or notification workflows. CloudTrail supplies API audit records that can be correlated with underlying permission changes. Across these patterns, treat DataZone as the discovery and workflow layer, not as a substitute for source-system authorization or monitoring.

- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: DataZone can ingest table metadata from the AWS Glue Data Catalog into project inventory for curation and publication. For example, a producer can catalog Glue tables describing an S3-based sales dataset, add business definitions, and publish the assets for discovery. Metadata ingestion does not copy the table's underlying data.
- **[AWS Lake Formation](https://blowstack.com/tools/cloud-services-hub/aws-lake-formation)**: DataZone uses Lake Formation for access fulfillment for supported Glue-backed assets. For example, an approved subscription can result in permissions for a consumer environment to query a governed table. Administrators must configure Lake Formation permissions, registered locations where required, and the relevant service roles.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: DataZone supports metadata ingestion and governed sharing workflows for supported Redshift configurations. For example, a finance team can publish warehouse tables and approve access for an analytics project. Redshift connectivity, credentials or secrets where required, and database permissions must be configured independently of catalog publication.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: Athena provides SQL query execution for data consumed through supported DataZone data lake environments. For example, an analyst can query an approved Glue-backed dataset using the project's configured environment. Athena query charges and access to query-result storage remain separate operational concerns.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: DataZone emits supported events that EventBridge rules can route to downstream automation. For example, a subscription workflow event can trigger a Lambda function to create a ticket or coordinate access fulfillment for an externally managed asset. Design handlers to tolerate duplicate delivery and reconcile workflow state through DataZone APIs.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records supported DataZone API activity for auditing and investigation. For example, a security team can investigate catalog configuration changes and correlate them with IAM, Lake Formation, or Redshift activity. Configure appropriate trail retention and centralized log storage for your audit requirements.
- **[Amazon Bedrock](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock)**: Amazon DataZone uses Amazon Bedrock to generate suggested business names and descriptions for cataloged data assets and their columns. Data producers can review these suggestions before publishing them to improve data discovery.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: Amazon DataZone can capture lineage from Spark jobs running on Amazon EMR through its OpenLineage integration. This connects transformations to their input and output datasets so catalog users can trace how data was produced.
- **[Amazon Managed Workflows for Apache Airflow (Amazon MWAA)](https://blowstack.com/tools/cloud-services-hub/amazon-managed-workflows-for-apache-airflow-(amazon-mwaa))**: Amazon DataZone can receive lineage events from Amazon MWAA workflows through Airflow's OpenLineage integration and a DataZone transport. This records relationships between workflow tasks and the datasets they read or produce.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon DataZone can catalog assets representing Amazon S3 objects, and its data lake environments use S3 locations for project data and Athena query results. For cataloged Glue tables backed by S3, DataZone uses Lake Formation to fulfill approved access.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: Amazon DataZone provides a SageMaker environment blueprint that provisions SageMaker Studio resources for project members. Users can discover and subscribe to governed data through DataZone and use that data in Studio for machine learning.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon DataZone supports interface VPC endpoints for private access to its APIs. DataZone environment configurations can also specify VPC networking for provisioned tools such as SageMaker Studio.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: Amazon DataZone domains, projects, environments, data sources, and other supported resources can be provisioned with AWS CloudFormation. DataZone also uses CloudFormation stacks to deploy resources defined by its environment blueprints.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config can record configuration changes for supported Amazon DataZone resource types, including domains, projects, and environments. This provides configuration history for auditing changes to DataZone resources.
- **[AWS IAM Identity Center (AWS Single Sign-On)](https://blowstack.com/tools/cloud-services-hub/aws-iam-identity-center-(aws-single-sign-on))**: Amazon DataZone integrates with IAM Identity Center to let workforce users sign in to its data portal using their organization’s identities. Administrators can make Identity Center users and groups available for membership in DataZone projects.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Amazon DataZone uses IAM policies and roles to authorize administrative operations, access data sources, and provision project environments. Its service and environment roles allow it to perform approved actions in associated AWS accounts.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: Amazon DataZone uses AWS KMS to encrypt domain data at rest and supports customer-managed keys. Key policies must allow the required DataZone operations so the service can encrypt and decrypt protected metadata.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: Amazon DataZone supports AWS PrivateLink through interface VPC endpoints. Applications can access supported DataZone API endpoints privately without requiring an internet gateway or NAT device.
- **[AWS Resource Access Manager (AWS RAM)](https://blowstack.com/tools/cloud-services-hub/aws-resource-access-manager-(aws-ram))**: Amazon DataZone uses AWS RAM to share a domain with associated AWS accounts. This allows projects and environments in those accounts to participate in the domain’s cross-account data discovery and sharing workflows.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: Amazon DataZone can use credentials stored in AWS Secrets Manager for supported data-source connections, including Amazon Redshift connections that use database credentials. The DataZone access role needs permission to retrieve the relevant secret.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: Amazon DataZone uses AWS STS to assume authorized roles when accessing data sources and managing environment resources. Its environment-credential functionality supplies temporary credentials for working with a project’s environment.

## Amazon DataZone exam questions

Real practice exam questions on Amazon DataZone, with the correct answer and its explanation.

### Question 1 (AIB-C01 (beta))

**Question:**

A telecommunications company is scaling AI initiatives across its business units. Teams can already find datasets through a shared data portal, but they interpret terms such as “active customer” differently. An AI pilot used a billing dataset as evidence of service usage, producing misleading results. Automatically generated dataset descriptions have not resolved these misunderstandings. The AI center of excellence (COE) must ensure that business definitions and appropriate-use guidance are validated before datasets are offered for enterprise reuse. Business units must retain data-use approval authority, and the COE cannot review every dataset. Which approach BEST meets these requirements?

**Correct answer:** Use Amazon DataZone with COE-managed glossary standards and a producer stewardship process. Business-unit stewards validate definitions and appropriate-use metadata before publication, while data owners retain subscription approval authority.

**Explanation:** This combines enterprise consistency with distributed accountability. The COE establishes common standards, knowledgeable business-unit stewards validate metadata before publication, and DataZone supports publishing and data-owner subscription workflows without making the COE review every asset.

### Question 2 (DEA-C01)

**Question:**

A company uses Amazon DataZone as its business data catalog. A producer project publishes AWS Glue Data Catalog tables whose Amazon S3 data is governed by AWS Lake Formation. Analysts can discover the published tables, read business descriptions, and submit subscription requests from consumer projects.

Data owners can approve requests, but automatic access provisioning fails. The provisioning logs show that the producer environment's manage-access IAM role cannot grant SELECT permissions to the consumer environment role. The manage-access role has SELECT on the tables without the grant option. Its IAM policy already allows the required Lake Formation API actions, and all other integration permissions are correctly configured.

The company must retain owner approval and automatically provision access for approved subscriptions without maintaining grants for individual consumers. Which change should a data engineer make?

**Correct answer:** Give the producer environment's manage-access role Lake Formation SELECT permission with the grant option on the published tables.

**Explanation:** DataZone uses the environment's manage-access role to provision Lake Formation permissions for supported managed assets after subscription approval. SELECT without the grant option lets the role read data but does not let it delegate SELECT to consumer environment roles. Adding the grant option addresses the identified failure while preserving the catalog's approval and automatic provisioning workflow.

## Practice Amazon DataZone in a full exam

Questions on Amazon DataZone 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): 12 questions
- [AIB-C01 (beta)](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist): 8 questions

## What is Amazon DataZone

Amazon DataZone provides a shared catalog and collaboration layer for organizational data. Data producers describe and publish assets, while consumers search the catalog, evaluate business and technical metadata, and request access. The service coordinates discovery and access workflows; it is not a replacement for object storage, a data warehouse, or a query engine.

A domain is the primary organizational boundary for a DataZone deployment. It contains catalog assets, projects, business glossaries, metadata forms, and governance configuration. Domain units can organize teams and assets within a domain and delegate selected administrative responsibilities. Plan this hierarchy around ownership and governance requirements rather than automatically creating a separate domain for every application.

An Amazon DataZone domain supports a maximum of 1 million data assets.

Projects group users who collaborate on a business objective. Environments provide the configured resources and permissions that project members use to publish or consume data. Environment blueprints and profiles control how these resources are provisioned. Administrators must configure the relevant IAM roles, account associations, and service permissions before projects can use integrated analytics resources.

Producers can configure data sources to import technical metadata from supported systems, including the AWS Glue Data Catalog and Amazon Redshift. Imported assets initially belong to a project's inventory, where producers can enrich descriptions, attach glossary terms, and populate custom metadata forms before publishing them to the business catalog. Schedule metadata ingestion according to the rate of schema changes and the freshness requirements of consumers.

Each data source supports a maximum of 25 data source runs per day.

Business description generation has a quota of 10,000 invocations per month. You can request an increase through AWS Support.

Consumers discover published assets through the data portal and submit subscription requests that explain their intended use. Authorized owners review requests and approve or reject them. For supported managed asset types, DataZone can coordinate access provisioning through integrated services such as AWS Lake Formation and Amazon Redshift. Other asset types can require an external fulfillment process. A catalog approval should not be treated as proof of effective access until the underlying grants and resource policies have been validated.

The catalog can also expose data quality results and lineage information. These capabilities help consumers evaluate whether data is suitable for a workload and understand upstream dependencies. Their coverage depends on which producers, jobs, and integrations supply the relevant metadata; publishing an asset does not automatically establish complete lineage or quality monitoring.

For production deployments, separate domain administration, data ownership, and consumption responsibilities. Monitor administrative and subscription activity, test access revocation, and account for cross-account permissions and encryption requirements. Budget separately for DataZone usage and the storage, queries, processing jobs, and other AWS resources used by project environments.

## Learn Amazon DataZone in lessons

5 short lessons on Amazon DataZone in 2 certification courses.

- AIB-C01 (beta): Amazon DataZone: discovering suitable data in the business catalog (Premium), https://app.blowstack.com/lessons/amazon-datazone-discovering-suitable-data-in-the-business-catalog-aib-c01
- DEA-C01: Amazon DataZone: building a business data catalog (Premium), https://app.blowstack.com/lessons/amazon-datazone-building-a-business-data-catalog-dea-c01
- AIB-C01 (beta): Amazon DataZone and AWS Glue: business and technical catalogs (Premium), https://app.blowstack.com/lessons/amazon-datazone-and-aws-glue-business-and-technical-catalogs-aib-c01
- DEA-C01: Amazon DataZone vs AWS Lake Formation: catalog collaboration and permission enforcement (Premium), https://app.blowstack.com/lessons/amazon-datazone-vs-aws-lake-formation-catalog-collaboration-and-permission-enforcement-dea-c01
- AIB-C01 (beta): AWS Lake Formation and Amazon DataZone: access control versus data discovery (Premium), https://app.blowstack.com/lessons/aws-lake-formation-and-amazon-datazone-access-control-versus-data-discovery-aib-c01

## Concepts related to Amazon DataZone

- [Data Cataloging](https://blowstack.com/tools/cloud-concepts-hub/data-cataloging): Data cataloging is the practice of maintaining a searchable inventory of data assets and metadata describing their meaning, ownership, origins, and permitted use.
- [Data Provenance](https://blowstack.com/tools/cloud-concepts-hub/data-provenance): Data provenance is the documented origin, ownership, and history of data, including how it was collected, transformed, and used.
- [Data Contracts](https://blowstack.com/tools/cloud-concepts-hub/data-contracts): Data contracts are explicit agreements between data producers and consumers that define a dataset’s structure, meaning, quality expectations, usage conditions, and change-management rules.
- [Data Mesh](https://blowstack.com/tools/cloud-concepts-hub/data-mesh): Data Mesh is a decentralized data operating model in which business domains own data products while sharing a self-service platform and federated governance standards.
- [Data Silos](https://blowstack.com/tools/cloud-concepts-hub/data-silos): Data silos are isolated collections of data that are difficult for other teams or systems to discover, access, interpret, or combine.
- [Data governance](https://blowstack.com/tools/cloud-concepts-hub/data-governance): Data governance is the system of policies, responsibilities, and controls that determines how data is collected, used, protected, and managed throughout its lifecycle.
