MDAA TS Docs
    Preparing search index...

    Interface LocationNfsProps

    NFS file system location configuration for DataSync transfers from on-premises Unix/Linux NFS servers. Agents connect to the NFS export and transfer data to AWS. NFS exports should be configured with no_root_squash or appropriate read permissions for all files and execute access on directories.

    Use cases: Linux NFS export migration to S3; Unix file system data transfer; NFS protocol synchronization

    AWS: DataSync LocationNFS resource (CfnLocationNFS)

    Validation: serverHostname and subdirectory required; one of agentNames or agentArns required (mutually exclusive)

    interface LocationNfsProps {
        agentArns?: string[];
        agentNames?: string[];
        nfsVersion?: string;
        serverHostname: string;
        subdirectory: string;
    }

    Hierarchy (View Summary)

    Index

    Properties

    agentArns? agentNames? nfsVersion? serverHostname subdirectory

    Properties

    agentArns?: string[]

    ARNs of DataSync agents for NFS connectivity. Used to construct the onPremConfig object. Use when agents are registered outside MDAA. Mutually exclusive with agentNames.

    Use cases: Externally managed agent references; Pre-existing agent reuse

    AWS: DataSync agent ARNs for NFS location onPremConfig

    Validation: Optional; mutually exclusive with agentNames; must be valid DataSync agent ARNs

    agentNames?: string[]

    Names of MDAA-generated DataSync agents from the agents config section. Resolved to agent ARNs and constructed as the onPremConfig object. Mutually exclusive with agentArns.

    Use cases: Referencing MDAA-managed agents by name; Multi-agent NFS connectivity

    AWS: Resolved to DataSync agent ARNs for NFS location onPremConfig

    Validation: Optional; mutually exclusive with agentArns; must reference valid generated agent names

    nfsVersion?: string

    NFS protocol version for mount options. MDAA custom parameter — the value is used to construct the MountOptions object.

    Use cases: NFS protocol version control; Compatibility with specific NFS server versions

    AWS: NFS mount options version for DataSync location

    Validation: Optional; valid values: AUTOMATIC | NFS3 | NFSv4_0 | NFSv4_1

    AUTOMATIC
    serverHostname: string

    Hostname or IP address of the NFS server. The on-premises DataSync agent uses this to mount the NFS export. Must be DNS-compliant or a valid IPv4 address.

    Use cases: NFS server identification; On-premises file server connectivity

    AWS: NFS server hostname for DataSync agent mounting

    Validation: Required; must be valid DNS name or IPv4 address

    subdirectory: string

    NFS export path or subdirectory for data access. Must use forward slashes. Use showmount -e nfs-server-name to list available exports. DataSync needs read access to all files and execute access on directories.

    Use cases: Scoped NFS export access; Subdirectory-level data transfer

    AWS: NFS subdirectory path for DataSync location

    Validation: Required; must be valid NFS export path with forward slashes

    Settings

    Member Visibility

    On This Page

    Properties