AWS fsx documentation change
Summary
Clarified 'Changed' export policy behavior and added note about S3 Standard storage class usage for auto-exported objects.
Security assessment
The policy clarification describes operational behavior (object recreation on changes), not a security fix. The storage class note is a feature documentation addition without security context.
Diff
diff --git a/fsx/latest/LustreGuide/autoexport-data-repo-dra.md b/fsx/latest/LustreGuide/autoexport-data-repo-dra.md index aa2f26d81..ce1a22230 100644 --- a//fsx/latest/LustreGuide/autoexport-data-repo-dra.md +++ b//fsx/latest/LustreGuide/autoexport-data-repo-dra.md @@ -34 +34 @@ The export policy specifies how you want FSx for Lustre to update your linked S3 - * **Changed** – FSx for Lustre automatically updates the S3 data repository only when an existing file in the file system is changed. For file content changes, the file must be closed before it's propagated to the S3 repository. Metadata changes (rename, ownership, permissions, and timestamps) are propagated when the operation is done. For renaming changes (including moves), the existing (pre-renamed) S3 object is deleted and a new S3 object is created with the new name. + * **Changed** – FSx for Lustre automatically updates the S3 data repository only when an existing file in the file system is changed. For file content changes, the file must be closed before it's propagated to the S3 repository. Metadata changes (rename, ownership, permissions, and timestamps) are propagated when the operation is done. For all changes (including both content and metadata changes), the existing corresponding S3 object is deleted and a new S3 object is created with the new content and/or metadata. @@ -46,0 +47,4 @@ For most use cases, we recommend that you configure an export policy of **New** +###### Note + +All S3 objects created by automatic export are written using the S3 Standard storage class. +