create_asset_filter
¶
create_asset_filter(
domain_identifier: DomainId,
asset_identifier: AssetId,
name: FilterName,
configuration: AssetFilterConfiguration,
*,
config_overrides: Optional[DataZoneClientConfig] = None,
description: Optional[Description] = None,
client_token: Optional[str] = None,
) -> CreateAssetFilterOutput
Creates a data asset filter.
Asset filters provide a sophisticated way to create controlled views of data assets by selecting specific columns or applying row-level filters. This capability is crucial for organizations that need to share data while maintaining security and privacy controls. For example, your database might be filtered to show only non-PII fields to certain users, or sales data might be filtered by region for different regional teams. Asset filters enable fine-grained access control while maintaining a single source of truth.
Prerequisites:
-
A valid domain (
--domain-identifier) must exist. -
A data asset (
--asset-identifier) must already be created under that domain. -
The asset must have the referenced columns available in its schema for column-based filtering.
-
You cannot specify both (
columnConfiguration,rowConfiguration)at the same time.
Parameters:
-
domain_identifier(DomainId) –The ID of the domain in which you want to create an asset filter.
-
asset_identifier(AssetId) –The ID of the data asset.
-
name(FilterName) –The name of the asset filter.
-
description(Optional[Description], default:None) –The description of the asset filter.
-
configuration(AssetFilterConfiguration) –The configuration of the asset filter.
-
client_token(Optional[str], default:None) –A unique, case-sensitive identifier that is provided to ensure the idempotency of the request.
Raises:
-
AccessDeniedException–You do not have sufficient access to perform this action.
-
ThrottlingException–The request was denied due to request throttling.
-
UnauthorizedException–You do not have permission to perform this action.
-
ConflictException–There is a conflict while performing this action.
-
InternalServerException–The request has failed because of an unknown error, exception or failure.
-
ResourceNotFoundException–The specified resource cannot be found.
-
ServiceQuotaExceededException–The request has exceeded the specified service quota.
-
ValidationException–The input fails to satisfy the constraints specified by the Amazon Web Services service.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_datazone/_services/data_zone.py
1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 | |