AWS eks documentation change
Summary
Replaced IAM policy ARN prefix with placeholder and converted console URL to plain text
Security assessment
Formatting changes for ARN examples and links. No security implications or security documentation enhancements.
Diff
diff --git a/eks/latest/userguide/fsx-csi-create.md b/eks/latest/userguide/fsx-csi-create.md index 906652417..24fb315a6 100644 --- a//eks/latest/userguide/fsx-csi-create.md +++ b//eks/latest/userguide/fsx-csi-create.md @@ -54 +54 @@ The following procedure shows you how to create an IAM role and attach the AWS m - --attach-policy-arn arn:aws:iam::aws:policy/AmazonFSxFullAccess \ + --attach-policy-arn <shared id="region.arn"/>iam::aws:policy/AmazonFSxFullAccess \ @@ -117 +117 @@ This procedure uses the [FSx for Lustre Container Storage Interface (CSI) driver - * **`subnetId` ** – The subnet ID that the Amazon FSx for Lustre file system should be created in. Amazon FSx for Lustre isn’t supported in all Availability Zones. Open the Amazon FSx for Lustre console at [https://console.aws.amazon.com/fsx/](https://console.aws.amazon.com/fsx/) to confirm that the subnet that you want to use is in a supported Availability Zone. The subnet can include your nodes, or can be a different subnet or VPC: + * **`subnetId` ** – The subnet ID that the Amazon FSx for Lustre file system should be created in. Amazon FSx for Lustre isn’t supported in all Availability Zones. Open the Amazon FSx for Lustre console at https://console.aws.amazon.com/fsx/ to confirm that the subnet that you want to use is in a supported Availability Zone. The subnet can include your nodes, or can be a different subnet or VPC: