AWS fsx documentation change
Summary
Added warning about recreating DRAs with same file system path and instructions for handling HSM state retention
Security assessment
Change addresses data management practices for HSM state retention, not security vulnerabilities. The added sudo command requires privileged access but doesn't introduce or document security features.
Diff
diff --git a/fsx/latest/LustreGuide/delete-linked-dra.md b/fsx/latest/LustreGuide/delete-linked-dra.md index b813f13c5..558daeaf8 100644 --- a//fsx/latest/LustreGuide/delete-linked-dra.md +++ b//fsx/latest/LustreGuide/delete-linked-dra.md @@ -40,0 +41,9 @@ After successfully deleting the data repository association, Amazon FSx returns +###### Recreating DRAs with the same file system path + +We do not recommend deleting and recreating data repository associations that use the same file system path. If you delete a DRA and later create a new DRA using the same file system path, some files may retain HSM state from the previously deleted DRA. + +If you need to export files from a recreated DRA that were managed by a previously deleted DRA, you need to mark those files as dirty using the command below and then run an export data repository task: + + + sudo lfs hsm_set --dirty file_path +