AWS fsx medium security documentation change
Summary
Added requirement to enter advanced mode before modifying flexcache write mode
Security assessment
The change enforces privilege escalation (advanced mode) before modifying critical configuration, addressing potential privilege control issues. This implements security best practices for access control.
Diff
diff --git a/fsx/latest/ONTAPGuide/create-flexcache.md b/fsx/latest/ONTAPGuide/create-flexcache.md index fb935e2b2..5f5e218e3 100644 --- a//fsx/latest/ONTAPGuide/create-flexcache.md +++ b//fsx/latest/ONTAPGuide/create-flexcache.md @@ -179 +179 @@ After successfully creating the SVM peering relationship, the next step is to cr -You can use the [`volume flexcache config modify -is-writeback-enabled {true|false}`](https://docs.netapp.com/us-en/ontap-cli-9151/volume-flexcache-config-modify.html#description) command to modify the write mode at any time. +You can use the [`volume flexcache config modify -is-writeback-enabled {true|false}`](https://docs.netapp.com/us-en/ontap-cli-9151/volume-flexcache-config-modify.html#description) command to modify the write mode. Before using this command, make sure you enter ONTAP CLI advanced mode by using the [`set -privilege advanced`](https://docs.netapp.com/us-en/ontap/system-admin/set-privilege-level-task.html) command.