AWS fsx: Clarify valid S3 path for FSx Lustre task completion reports
Summary
Added a note explaining that the task completion report path must reside within the S3 location the file system is linked to (the DataRepositoryPath of an association or the ExportPath), with a valid/invalid path example.
Security assessment
The added note is a functional clarification about where report files can be written relative to the linked S3 data repository; it does not describe a security control, vulnerability, or credential/permission change.
Evidence
+The report path must be within the Amazon S3 location that your file system is linked to. That location depends on how your file system is configured:
Diff
diff --git a/fsx/latest/LustreGuide/task-completion-report.md b/fsx/latest/LustreGuide/task-completion-report.md index ad8d2ef..ce6fe46 100644 --- a//fsx/latest/LustreGuide/task-completion-report.md +++ b//fsx/latest/LustreGuide/task-completion-report.md @@ -12,0 +13,13 @@ Amazon FSx delivers the report to the file system's linked data repository in Am +###### Note + +The report path must be within the Amazon S3 location that your file system is linked to. That location depends on how your file system is configured: + + * The `DataRepositoryPath` of one of the associations, if your file system has data repository associations + + * The `ExportPath`, if your file system was created with an `ImportPath` and an `ExportPath` + + + + +For example, if an association links to `s3://amzn-s3-demo-bucket/myPrefix`, then `s3://amzn-s3-demo-bucket/myPrefix/reports` is valid. The path `s3://amzn-s3-demo-bucket/reports` is not. +