Creating an Export

1. Open the navigation menu  and select Storage. Under File Storage, select File Systems.
2. Select a compartment that you have permission to work in.
3. On the File Systems list page, select the file system that you want to work with. If you need help finding the list page or the file system, see Listing File Systems.
4. On the details page, select Exports.
5. Select Create export.
6. To accept the default settings, select Create. To customize the export, continue with the following steps.
7. In the Export information section, specify details for the export associated with the file system:

   • Export path: The File Storage creates a default export path using the file system name. Optionally, replace the default export path with a new path, starting with a slash (/). For example, /fss. This value specifies the mount path to the file system (relative to the mount target IP address or hostname). Avoid entering confidential information. For more information, see Paths in File Systems.

   • Use secure export options: Turn on this option to require NFS clients to use a privileged port (1–1023) as the source port. This option enhances security because only clients with root privileges can use a privileged source port. After the export is created, you can edit the export options to adjust security. For more information, see Working with NFS Exports and Export Options.

     Caution
     
     If you leave the Use secure export options option turned off, unprivileged users can read and change any file or directory on the target file system.

   • Use LDAP for group list: Turn on this option to use a configured LDAP server to map the user to UNIX groups instead of the groups listed in the NFS request's RPC header when using AUTH_SYS authentication. For more information, see Using LDAP for Authorization. This option doesn't affect Kerberos authentication, because mapping is always enabled with Kerberos.

8. In the Resource locks section, select the type of resource lock to apply:
   • No lock: No restrictions.
   • Delete: Prevents deleting the resource.
   • Full: Prevents all modifications except reading the resource.
9. In the Mount target information section, specify information for the mount target associated with the file system:
   • Select an existing mount target: Select this option to associate the file system with a mount target that you already created.

     If there aren't any mount targets in the current combination of availability domain and compartment, this option is disabled. You can select a different compartment or create a new mount target.

   • Create new mount target: Select this option to create a new mount target associated with this file system.
     Important
     
     The mount target is always in the same availability domain as the file system. While you can access mount targets from any Availability domain in a region, for best performance, ensure the mount target and file system are in the same availability domain as the Compute instances that access them. For more information, see Regions and Availability Domains.
10. If you're creating a new mount target, provide the following information:
    1. Compartment: Select the compartment you want to create the mount target in.

    2. New mount target name: Optionally, enter a friendly name for the mount target. It doesn't have to be unique; an Oracle Cloud Identifier (OCID) uniquely identifies the mount target. Avoid entering confidential information.

       Note
       
       The mount target name is different from the DNS hostname, which is specified under IP details.
    3. Virtual cloud network compartment: Select the compartment that contains the virtual cloud network (VCN) where you want to create the mount target.
    4. Virtual cloud network: Select the VCN where you want to create the new mount target.
    5. Subnet compartment: Select the compartment containing the subnet within the VCN to attach the mount target to.
    6. Subnet: Select a subnet to attach the mount target to. Subnets can be either AD-specific or regional (regional subnets have "regional" after the name). For more information, see VCN and Subnet Management.
       Caution
       
       Each mount target requires three internal IP addresses in the subnet to function. Don't use /30 or smaller subnets for mount target creation because there are not enough available IP addresses. Two of the IP addresses are used during mount target creation and the third IP address must remain available for high availability failover.
    7. Use network security groups to control traffic: Turn on this option to add this mount target to an existing network security group (NSG). Select a Network security groups compartment and then a Network security group under that compartment.
       Note
       
       The rules for the NSG you select must allow traffic to the mount target's VNIC using specific protocols and ports. For more information, see Configuring VCN Security Rules for File Storage.
    8. IP details:
       • IP address: Optionally, specify an unused IP address in the subnet you selected for the mount target.

       • Hostname: Optionally, specify a hostname to assign to the mount target.

         Note
         
         The File Storage constructs a fully qualified domain name (FQDN) by combining the hostname with the FQDN of the subnet the mount target is find in.

         For example, myhostname.subnet123.dnslabel.oraclevcn.com.

         After it's created, you can change the hostname in the mount target's details page. For more information, see Managing Mount Targets.

         Important
         
         If you enable Kerberos authentication for a mount target in a VCN that uses the default Internet and VCN Resolver for DNS, you must specify a hostname.
    9. Tags: (Optional) Expand the Tags section and select Add tag.

       If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, skip this option or ask an administrator. You can apply tags later.

11. Select Create to create the export. You can also select Cancel to exit without creating, or (optional) select Save as stack to save the configuration as a Resource Manager stack. For more information, see Managing Stacks.

Next, mount the file system from an instance so that you can read and write directories and files in the file system. For instructions on obtaining mount commands for the OS and mounting the file system, see Mounting File Systems.