export changes from Lustre filesystem

Currently, automatic export is only supported on the Persistent 2 deployment type. https://docs.aws.amazon.com/fsx/latest/LustreGuide/export-changed-data-meta-dra.html

On Persistent 1 and Scratch file systems, you can use a data repository task to export changes made on the file system to the S3 bucket. https://docs.aws.amazon.com/fsx/latest/LustreGuide/export-data-repo-task-dra.html

Hello,

from the SharedStorage.FsxLustreSettings.ExportPath documentation:

ExportPath (Optional, String)

The path in Amazon S3 where the root of your FSx for Lustre file system is exported. This setting is only supported when the ImportPath parameter is specified. The path must use the same Amazon S3 bucket as specified in ImportPath. You can provide an optional prefix to which new and changed data is to be exported from your FSx for Lustre file system. If an ExportPath value is not provided, FSx for Lustre sets a default export path, s3://import-bucket/FSxLustre[creation-timestamp]. The timestamp is in UTC format, for example s3://import-bucket/FSxLustre20181105T222312Z.

The Amazon S3 export bucket must be the same as the import bucket specified by ImportPath. If you only specify a bucket name, such as s3://import-bucket, you get a 1:1 mapping of file system objects to Amazon S3 bucket objects. This mapping means that the input data in Amazon S3 is overwritten on export. If you provide a custom prefix in the export path, such as s3://import-bucket/[custom-optional-prefix], FSx for Lustre exports the contents of your file system to that export prefix in the Amazon S3 bucket.

So, the intended use of SharedStorage.FsxLustreSettings.ExportPath and SharedStorage.FsxLustreSettings.ImportPath is the following:

• you can set up an ImportPath to populate your Lustre file system with data coming from an S3 bucket;
• you can use ExportPath to automatically export data to the same bucket, either to a subfolder of the bucket (the default should be to create a subfolder with a timestamp of the creation, alternative you can provide a custom subfolder), or overwriting the original bucket data (by providing the exact S3 path as ImportPath).

This functionality is not available for PERSISITENT_2 file systems, because in that case there's another mechanism internal to the FSxForLustre service.