CLOUD SERVICE · AWS

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

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.

Cloud Services Hub →

What is Amazon DataZone

Read the extensive description

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.

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.

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.

Key Amazon DataZone Features

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.

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.

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.

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.

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.

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.

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.

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.

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.

Amazon DataZone Use Cases

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.

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.

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.

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.

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.

Amazon DataZone pricing models

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.

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.

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.

Compute usage

DataZone meters compute used for applicable service processing activities. Consider metadata ingestion frequency and processing volume when estimating usage.

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.

Services Amazon DataZone integrates 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.

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.

Open Amazon Athena →

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.

Open AWS Glue →

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.

Open AWS Lake Formation →

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.

Open Amazon Redshift →

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.

Open Amazon EventBridge →

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.

Open AWS CloudTrail →