Struct aws_sdk_datasync::operation::create_location_nfs::builders::CreateLocationNfsFluentBuilder

source ·

pub struct CreateLocationNfsFluentBuilder { /* private fields */ }

Expand description

Fluent builder constructing a request to CreateLocationNfs.

Defines a file system on a Network File System (NFS) server that can be read from or written to.

Implementations§

source §

impl CreateLocationNfsFluentBuilder

source

pub async fn customize( self ) -> Result<CustomizableOperation<CreateLocationNfs, AwsResponseRetryClassifier>, SdkError<CreateLocationNfsError>>

Consume this builder, creating a customizable operation that can be modified before being sent. The operation’s inner http::Request can be modified as well.

source

pub async fn send( self ) -> Result<CreateLocationNfsOutput, SdkError<CreateLocationNfsError>>

Sends the request and returns the response.

If an error occurs, an SdkError will be returned with additional details that can be matched against.

By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.

source

pub fn subdirectory(self, input: impl Into<String>) -> Self

The subdirectory in the NFS file system that is used to read data from the NFS source location or write data to the NFS destination. The NFS path should be a path that's exported by the NFS server, or a subdirectory of that path. The path should be such that it can be mounted by other NFS clients in your network.

To see all the paths exported by your NFS server, run "showmount -e nfs-server-name" from an NFS client that has access to your server. You can specify any directory that appears in the results, and any subdirectory of that directory. Ensure that the NFS export is accessible without Kerberos authentication.

To transfer all the data in the folder you specified, DataSync needs to have permissions to read all the data. To ensure this, either configure the NFS export with no_root_squash, or ensure that the permissions for all of the files that you want DataSync allow read access for all users. Doing either enables the agent to read the files. For the agent to access directories, you must additionally enable all execute access.

If you are copying data to or from your Snowcone device, see NFS Server on Snowcone for more information.

For information about NFS export configuration, see 18.7. The /etc/exports Configuration File in the Red Hat Enterprise Linux documentation.

source

pub fn set_subdirectory(self, input: Option<String>) -> Self

The subdirectory in the NFS file system that is used to read data from the NFS source location or write data to the NFS destination. The NFS path should be a path that's exported by the NFS server, or a subdirectory of that path. The path should be such that it can be mounted by other NFS clients in your network.

To see all the paths exported by your NFS server, run "showmount -e nfs-server-name" from an NFS client that has access to your server. You can specify any directory that appears in the results, and any subdirectory of that directory. Ensure that the NFS export is accessible without Kerberos authentication.

To transfer all the data in the folder you specified, DataSync needs to have permissions to read all the data. To ensure this, either configure the NFS export with no_root_squash, or ensure that the permissions for all of the files that you want DataSync allow read access for all users. Doing either enables the agent to read the files. For the agent to access directories, you must additionally enable all execute access.

If you are copying data to or from your Snowcone device, see NFS Server on Snowcone for more information.

For information about NFS export configuration, see 18.7. The /etc/exports Configuration File in the Red Hat Enterprise Linux documentation.

source

pub fn server_hostname(self, input: impl Into<String>) -> Self

The name of the NFS server. This value is the IP address or Domain Name Service (DNS) name of the NFS server. An agent that is installed on-premises uses this hostname to mount the NFS server in a network.

If you are copying data to or from your Snowcone device, see NFS Server on Snowcone for more information.

This name must either be DNS-compliant or must be an IP version 4 (IPv4) address.

source

pub fn set_server_hostname(self, input: Option<String>) -> Self

The name of the NFS server. This value is the IP address or Domain Name Service (DNS) name of the NFS server. An agent that is installed on-premises uses this hostname to mount the NFS server in a network.

If you are copying data to or from your Snowcone device, see NFS Server on Snowcone for more information.

This name must either be DNS-compliant or must be an IP version 4 (IPv4) address.

source

pub fn on_prem_config(self, input: OnPremConfig) -> Self

Contains a list of Amazon Resource Names (ARNs) of agents that are used to connect to an NFS server.

If you are copying data to or from your Snowcone device, see NFS Server on Snowcone for more information.

source

pub fn set_on_prem_config(self, input: Option<OnPremConfig>) -> Self

Contains a list of Amazon Resource Names (ARNs) of agents that are used to connect to an NFS server.

If you are copying data to or from your Snowcone device, see NFS Server on Snowcone for more information.

source

pub fn mount_options(self, input: NfsMountOptions) -> Self

The NFS mount options that DataSync can use to mount your NFS share.

source

pub fn set_mount_options(self, input: Option<NfsMountOptions>) -> Self

The NFS mount options that DataSync can use to mount your NFS share.

source

pub fn tags(self, input: TagListEntry) -> Self

Appends an item to Tags.

To override the contents of this collection use set_tags.

The key-value pair that represents the tag that you want to add to the location. The value can be an empty string. We recommend using tags to name your resources.

source

pub fn set_tags(self, input: Option<Vec<TagListEntry>>) -> Self

The key-value pair that represents the tag that you want to add to the location. The value can be an empty string. We recommend using tags to name your resources.