AWS Security ChangesHomeSearch

AWS AmazonS3: Renumber access point tagging policy sections, remove tag/delegate examples

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

File: AmazonS3/latest/userguide/access-points-tagging.md · Type: iam

Summary

Removed two example policies (an access point policy restricting GetObject by matching access point and principal `project` tags, and a delegate bucket policy JSON block) and renumbered the remaining sections (1.2–1.4).

Security assessment

The diff only renumbers headings and deletes JSON policy examples; the surviving text still references tag-based access control but no new security guidance or fix is introduced. Editorial restructuring, no vulnerability addressed.

Evidence

+#### 1.2 - IAM policy to modify tags on existing resources maintaining tagging governence

Diff

diff --git a/AmazonS3/latest/userguide/access-points-tagging.md b/AmazonS3/latest/userguide/access-points-tagging.md
index 60f0218..99e72fc 100644
--- a//AmazonS3/latest/userguide/access-points-tagging.md
+++ b//AmazonS3/latest/userguide/access-points-tagging.md
@@ -82,26 +82 @@ In this IAM policy, users or roles with this policy can only create access point
-#### 1.2 - Access Point policy to restrict operations on the access point using tags
-
-In this Access Point policy, IAM principals (users and roles) can perform operations using the `GetObject` action on the access point only if the value of the access point's `project` tag matches the value of the principal's `project` tag.
-    
-    
-    {
-      "Version": "2012-10-17",
-      "Statement": [
-        {
-          "Sid": "AllowObjectOperations",
-          "Effect": "Allow",
-          "Principal": {
-            "AWS": "111122223333"
-          },
-          "Action": "s3:GetObject",
-          "Resource": "arn:aws::s3:region:111122223333:accesspoint/my-access-point",
-          "Condition": {
-            "StringEquals": {
-              "aws:ResourceTag/project": "${aws:PrincipalTag/project}"
-            }
-          }
-        }
-      ]
-    }
-
-#### 1.3 - IAM policy to modify tags on existing resources maintaining tagging governence
+#### 1.2 - IAM policy to modify tags on existing resources maintaining tagging governence
@@ -139 +114 @@ In this IAM policy, IAM principals (users or roles) can modify tags on an access
-#### 1.4 - Using the s3:AccessPointTag condition key
+#### 1.3 - Using the s3:AccessPointTag condition key
@@ -162 +137 @@ In this IAM policy, the condition statement allows access to the bucket's data i
-#### 1.5 - Using a bucket delegate policy
+#### 1.4 - Using a bucket delegate policy
@@ -166,20 +141 @@ In Amazon S3, you can delegate access to or control of your S3 bucket policy to
-If using a delegate bucket policy, such as the following: 
-    
-    
-    {
-      "Version": "2012-10-17",
-        "Statement": {
-          "Principal": {"AWS": "*"},
-            "Effect": "Allow",
-            "Action": ["s3:*"],
-            "Resource":["arn:aws::s3:::amzn-s3-demo-bucket/*", "arn:aws::s3:::amzn-s3-demo-bucket"],
-               "Condition": {
-                 "StringEquals" : {
-                    "s3:DataAccessPointAccount" : "111122223333"
-                 }
-               }
-        }
-    }
-    
-
-In the following IAM policy, the condition statement allows access to the bucket's data if the access point has the tag key `Environment` and tag value `Production`. 
+If you use a delegate bucket policy, you can use an IAM policy like the following. The condition statement allows access to the bucket\'s data if the access point has the tag key `Environment` and tag value `Production`.