MDAA TS Docs
    Preparing search index...
    interface SageMakerProjectProps {
        dataSourceDefaults?: DataSourceDefaultsProps;
        dataSources?: { [name: string]: DataSourceProps };
        domainUnit?: string;
        environmentConfigs?: { [name: string]: ProjectEnvironmentConfiguration };
        glossaries?: { [glossaryName: string]: GlossaryProps };
        groups?: { [id: string]: string };
        metadataForms?: { [formName: string]: MetadataFormProps };
        nameOverride?: string;
        ownerGroups?: { [id: string]: string };
        ownerUsers?: { [id: string]: string };
        profileName: string;
        users?: { [id: string]: string };
    }
    Index

    Properties

    dataSourceDefaults?: DataSourceDefaultsProps

    Default values for publishOnImport, enableSetting, schedule, recommendation, autoImportDataQualityResult, and filterExpressions, inherited by every Glue (databaseName) entry in dataSources. A data source that specifies one of these fields itself overrides the default for that field entirely (fields are not deep-merged). Has no effect on an s3 data source, which has no equivalent properties.

    Use cases: Consistent run schedule/publishing behavior across many data sources in a producer project

    AWS: AWS::DataZone::DataSource (defaults applied per-data-source at synth time)

    Validation: Optional; DataSourceDefaultsProps

    - no defaults; each data source uses DataZone's own defaults for unset fields
    
    dataSources?: { [name: string]: DataSourceProps }

    Data sources to import into the project. Each entry is either a databaseName, which imports a Glue database and grants the project's environment user Lake Formation read permissions on it and its tables, or an s3, which creates a DataZone S3 connection and grants the project's environment user role IAM read (list and get) on the registered bucket and prefix.

    Use cases: Importing existing Glue databases into SageMaker projects; Onboarding raw S3 data lake locations into a SMUS project's data catalog; Data asset discovery

    AWS: DataZone data sources with Glue run configuration; DataZone connections with S3 properties (AWS::DataZone::Connection)

    Validation: Optional; map of data source name to DataSourceProps

    domainUnit?: string

    Domain unit path where the project will be created (e.g., /some/domain/unit).

    Use cases: Project organizational placement; Governance scope targeting

    AWS: DataZone domain unit for project placement

    Validation: Optional; slash-delimited domain unit path

    environmentConfigs?: { [name: string]: ProjectEnvironmentConfiguration }

    Per-environment configuration overrides for this project's environments.

    Use cases: Project-specific environment customization

    AWS: DataZone project environment configurations

    Validation: Optional; map of environment name to ProjectEnvironmentConfiguration

    glossaries?: { [glossaryName: string]: GlossaryProps }

    Business glossaries to create, owned by this project. A metadata form field's glossaryId may reference a declared glossary here as "<glossaryName>", or a declared term as "<glossaryName>.<termName>", which MDAA resolves to the glossary's deploy-time ID and wires as a CDK dependency, or it may continue to use a literal, pre-existing glossary ID string, unchanged. The map key is used as the glossary's stable identifier; renaming a key replaces that glossary (create-then-delete).

    Use cases: Business glossary/terminology as code; Linking standardized terms to metadata forms

    AWS: DataZone business glossaries and terms, owned by the project

    Validation: Optional; map of glossary name to GlossaryProps

    groups?: { [id: string]: string }

    MDAA group configuration names that receive PROJECT_CONTRIBUTOR designation with contributor-level access to the project.

    Use cases: Team-based project contribution; Group standard access

    AWS: DataZone project membership with PROJECT_CONTRIBUTOR role

    Validation: Optional; map of ID to group config name; names must exist in module groups config

    metadataForms?: { [formName: string]: MetadataFormProps }

    Metadata form types to create, owned by this project. Each form is defined by a set of fields; MDAA assembles the Smithy model (setting the namespace to the domain ID and the structure name to the form name). Forms are usable across the domain to attach standardized metadata to assets. The map key is used as the form's stable identifier; renaming a key replaces that form type (create-then-delete).

    Use cases: Data governance metadata standards; Asset metadata enforcement; Searchable custom attributes

    AWS: DataZone metadata form types (AWS::DataZone::FormType) owned by the project

    Validation: Optional; map of form name to MetadataFormProps; form name must be a valid Smithy structure name

    nameOverride?: string

    Exact DataZone project name, used verbatim and bypassing MDAA naming conventions. Intended for the user-facing SMUS project title, which is a free-form label chosen by the business and is not derivable from org/env/domain/module metadata. All other resources created by the module keep MDAA naming.

    AWS: AWS::DataZone::Project Name

    Validation: Optional; 1-64 chars matching ^[\w -]+$ (spaces and mixed case allowed); must be unique within the DataZone domain.

    ownerGroups?: { [id: string]: string }

    MDAA group configuration names (from the SageMaker module groups section) that receive PROJECT_OWNER designation with full administrative access to the project. These are not DataZone group names or Identity Center group identifiers.

    Use cases: Team-based project ownership; Group admin access

    AWS: DataZone project membership with PROJECT_OWNER role

    Validation: Optional; map of ID to group config name; names must exist in module groups config

    ownerUsers?: { [id: string]: string }

    MDAA user configuration names (from the SageMaker module users section) that receive PROJECT_OWNER designation with full administrative access to the project. These are not DataZone usernames or Identity Center identifiers.

    Use cases: User-based project ownership; Full project admin access

    AWS: DataZone project membership with PROJECT_OWNER role

    Validation: Optional; map of ID to user config name; names must exist in module users config

    profileName: string

    Name of the project profile to use for this project. The profile must target the same account as the project.

    Use cases: Profile-based project creation; Environment template selection

    AWS: DataZone project profile reference

    Validation: Required; string; must match a key in projectProfiles config

    users?: { [id: string]: string }

    MDAA user configuration names that receive PROJECT_CONTRIBUTOR designation with contributor-level access to the project.

    Use cases: User-based project contribution; Standard project access

    AWS: DataZone project membership with PROJECT_CONTRIBUTOR role

    Validation: Optional; map of ID to user config name; names must exist in module users config