AWS Security ChangesHomeSearch

AWS AmazonS3: Replace S3 Files access point policy JSON with prose description

Service: AmazonS3 · 2026-10-03 · Documentation low

File: AmazonS3/latest/userguide/s3-files-access-point-policy-examples.md · Type: authz

Summary

Removed the example file system policy JSON (AllowComputeAOnlyViaSpecificAP / DenyComputeAIfWrongAP) and replaced it with prose stating a role is allowed only when targeting fsap-ID and explicitly denied otherwise, noting explicit deny overrides identity policies.

Security assessment

The change condenses an existing authorization example into descriptive text; the explicit-deny behavior described was already documented and no new control or fix is introduced. No specific vulnerability referenced.

Evidence

+A role is allowed to mount and write only when the request targets `fsap-ID`, and is explicitly denied on every other access point on this file system. An explicit deny in a resource policy cannot be overridden by identity policies, so this restriction holds even if a broader IAM policy is attached to the role later.

Diff

diff --git a/AmazonS3/latest/userguide/s3-files-access-point-policy-examples.md b/AmazonS3/latest/userguide/s3-files-access-point-policy-examples.md
index 5695eaa..e9410b1 100644
--- a//AmazonS3/latest/userguide/s3-files-access-point-policy-examples.md
+++ b//AmazonS3/latest/userguide/s3-files-access-point-policy-examples.md
@@ -25,35 +25 @@ This pattern applies when a role (for example, an EC2 instance role or an ECS ta
-**Example file system policy:**
-    
-    
-    {
-      "Version": "2012-10-17",
-      "Statement": [
-        {
-          "Sid": "AllowComputeAOnlyViaSpecificAP",
-          "Effect": "Allow",
-          "Principal": { "AWS": "arn:aws:iam::ACCOUNT:role/compute-a-role" },
-          "Action": [
-            "s3files:ClientMount",
-            "s3files:ClientWrite"
-          ],
-          "Condition": {
-            "StringEquals": {
-              "s3files:AccessPointArn": "arn:aws:s3files:REGION:ACCOUNT:file-system/fs-ID/access-point/fsap-ID"
-            }
-          }
-        },
-        {
-          "Sid": "DenyComputeAIfWrongAP",
-          "Effect": "Deny",
-          "Principal": { "AWS": "arn:aws:iam::ACCOUNT:role/compute-a-role" },
-          "Action": "s3files:Client*",
-          "Condition": {
-            "StringNotEquals": {
-              "s3files:AccessPointArn": "arn:aws:s3files:REGION:ACCOUNT:file-system/fs-ID/access-point/fsap-ID"
-            }
-          }
-        }
-      ]
-    }
-
-The role `compute-a-role` is allowed to mount and write only when the request targets `fsap-ID`, and is explicitly denied on every other access point on this file system. An explicit deny in a resource policy cannot be overridden by identity policies, so this restriction holds even if a broader IAM policy is attached to the role later.
+A role is allowed to mount and write only when the request targets `fsap-ID`, and is explicitly denied on every other access point on this file system. An explicit deny in a resource policy cannot be overridden by identity policies, so this restriction holds even if a broader IAM policy is attached to the role later.