AWS Security ChangesHomeSearch

AWS AmazonRDS: Aurora analytics IAM reference: placeholder IDs and table formatting cleanup

Service: AmazonRDS · 2026-11-07 · Documentation low

File: AmazonRDS/latest/AuroraUserGuide/aurora-analytics-iam-policies-reference.md

Summary

Cosmetic and editorial update to the Aurora PostgreSQL analytics IAM policies reference: replaces the sample AWS account ID 123456789012 with 111122223333 (and 111122223333/444455556666 in the cross-account example), swaps sample UUIDs/keys for the EXAMPLE-style placeholders, fixes markdown table header rows that had collapsed into prose (removing stray trailing spaces), corrects a missing period, and converts bolded list-item colons to en dashes. No policy guidance, permissions, or security statements were added or changed.

Security assessment

The diff is a documentation hygiene pass: every substantive line replaces a sample account ID, key ID, or table UUID with a different illustrative placeholder, and the remaining edits fix markdown table header formatting and punctuation. The security guidance itself (least privilege, scoping Resource ARNs, KMS, aws:SourceAccount/aws:SourceArn conditions) is unchanged apart from punctuation, so no new security feature, hardening step, or vulnerability fix is introduced. Severity is therefore low.

Evidence

+                    "arn:aws:glue:us-east-1:111122223333:catalog",

Diff

diff --git a/AmazonRDS/latest/AuroraUserGuide/aurora-analytics-iam-policies-reference.md b/AmazonRDS/latest/AuroraUserGuide/aurora-analytics-iam-policies-reference.md
index c5ecf31..8aa1c19 100644
--- a//AmazonRDS/latest/AuroraUserGuide/aurora-analytics-iam-policies-reference.md
+++ b//AmazonRDS/latest/AuroraUserGuide/aurora-analytics-iam-policies-reference.md
@@ -34 +34 @@ The following table summarizes the permissions that Aurora PostgreSQL requires f
-Required permissions by data format and access path Data format and access path | Service | Required permissions | Resources  
+Data format and access path | Service | Required permissions | Resources  
@@ -58 +58 @@ Three points affect how much you need to grant:
-These example policies use `amzn-s3-demo-bucket` as the bucket name, `amzn-s3-demo-table-bucket` as the Amazon S3 Tables table bucket name, and `123456789012` as the AWS account ID. To use these policies, replace the `user input placeholders` with your own information, and scope each `Resource` element to only the data that your foreign tables reference.
+These example policies use `amzn-s3-demo-bucket` as the bucket name, `amzn-s3-demo-table-bucket` as the Amazon S3 Tables table bucket name, and `111122223333` as the AWS account ID. To use these policies, replace the `user input placeholders` with your own information, and scope each `Resource` element to only the data that your foreign tables reference.
@@ -121,4 +121,4 @@ The following example policy grants permission to query Iceberg tables that are
-                    "arn:aws:glue:us-east-1:123456789012:catalog",
-                    "arn:aws:glue:us-east-1:123456789012:database/analytics_db",
-                    "arn:aws:glue:us-east-1:123456789012:table/analytics_db/orders",
-                    "arn:aws:glue:us-east-1:123456789012:table/analytics_db/customers"
+                    "arn:aws:glue:us-east-1:111122223333:catalog",
+                    "arn:aws:glue:us-east-1:111122223333:database/analytics_db",
+                    "arn:aws:glue:us-east-1:111122223333:table/analytics_db/orders",
+                    "arn:aws:glue:us-east-1:111122223333:table/analytics_db/customers"
@@ -159 +159 @@ Amazon S3 Tables supports two access paths, and each requires a different set of
-The following example policy grants permission to query an Amazon S3 Tables table through an AWS Glue ARN under the `s3tablescatalog` federated catalog, such as `arn:aws:glue:us-east-1:123456789012:table/s3tablescatalog/amzn-s3-demo-table-bucket/my_namespace/orders`.
+The following example policy grants permission to query an Amazon S3 Tables table through an AWS Glue ARN under the `s3tablescatalog` federated catalog, such as `arn:aws:glue:us-east-1:111122223333:table/s3tablescatalog/amzn-s3-demo-table-bucket/my_namespace/orders`.
@@ -170,3 +170,3 @@ The following example policy grants permission to query an Amazon S3 Tables tabl
-                    "arn:aws:glue:us-east-1:123456789012:catalog/s3tablescatalog/amzn-s3-demo-table-bucket",
-                    "arn:aws:glue:us-east-1:123456789012:database/s3tablescatalog/amzn-s3-demo-table-bucket/my_namespace",
-                    "arn:aws:glue:us-east-1:123456789012:table/s3tablescatalog/amzn-s3-demo-table-bucket/my_namespace/orders"
+                    "arn:aws:glue:us-east-1:111122223333:catalog/s3tablescatalog/amzn-s3-demo-table-bucket",
+                    "arn:aws:glue:us-east-1:111122223333:database/s3tablescatalog/amzn-s3-demo-table-bucket/my_namespace",
+                    "arn:aws:glue:us-east-1:111122223333:table/s3tablescatalog/amzn-s3-demo-table-bucket/my_namespace/orders"
@@ -185,2 +185,2 @@ The following example policy grants permission to query an Amazon S3 Tables tabl
-                    "arn:aws:s3tables:us-east-1:123456789012:bucket/amzn-s3-demo-table-bucket",
-                    "arn:aws:s3tables:us-east-1:123456789012:bucket/amzn-s3-demo-table-bucket/table/*"
+                    "arn:aws:s3tables:us-east-1:111122223333:bucket/amzn-s3-demo-table-bucket",
+                    "arn:aws:s3tables:us-east-1:111122223333:bucket/amzn-s3-demo-table-bucket/table/*"
@@ -194 +194 @@ The following example policy grants permission to query an Amazon S3 Tables tabl
-The following example policy grants permission to query an Amazon S3 Tables table by its table ARN, such as `arn:aws:s3tables:us-east-1:123456789012:bucket/amzn-s3-demo-table-bucket/table/1234abcd-12ab-34cd-56ef-1234567890ab`. This access path doesn't involve AWS Glue, and no AWS Glue permissions are required.
+The following example policy grants permission to query an Amazon S3 Tables table by its table ARN, such as `arn:aws:s3tables:us-east-1:111122223333:bucket/amzn-s3-demo-table-bucket/table/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111`. This access path doesn't involve AWS Glue, and no AWS Glue permissions are required.
@@ -210,2 +210,2 @@ The following example policy grants permission to query an Amazon S3 Tables tabl
-                    "arn:aws:s3tables:us-east-1:123456789012:bucket/amzn-s3-demo-table-bucket",
-                    "arn:aws:s3tables:us-east-1:123456789012:bucket/amzn-s3-demo-table-bucket/table/*"
+                    "arn:aws:s3tables:us-east-1:111122223333:bucket/amzn-s3-demo-table-bucket",
+                    "arn:aws:s3tables:us-east-1:111122223333:bucket/amzn-s3-demo-table-bucket/table/*"
@@ -227 +227 @@ Grants permission to resolve the table through AWS Glue Data Catalog. Amazon S3
-Grants permission to resolve and read the table through Amazon S3 Tables. All four actions are required, and each one authorizes a distinct step of table resolution:
+Grants permission to resolve and read the table through Amazon S3 Tables. All four actions are required, and each one authorizes a distinct step of table resolution.
@@ -229 +229 @@ Grants permission to resolve and read the table through Amazon S3 Tables. All fo
-Amazon S3 Tables actions and the steps they authorize Action | Authorizes  
+Action | Authorizes  
@@ -251 +251 @@ If your data is encrypted with server-side encryption using AWS KMS keys (SSE-KM
-        "Resource": "arn:aws:kms:us-east-1:123456789012:key/1234abcd-12ab-34cd-56ef-1234567890ab"
+        "Resource": "arn:aws:kms:us-east-1:111122223333:key/a1b2c3d4-5678-90ab-cdef-EXAMPLE22222"
@@ -258 +258 @@ For a KMS key that is owned by another account, the key policy in the owning acc
-When another account owns your data, both accounts must allow the action. In the following examples, a cluster role in account `123456789012` reads Parquet files from a bucket that is owned by account `111122223333`.
+When another account owns your data, both accounts must allow the action. In the following examples, a cluster role in account `111122223333` reads Parquet files from a bucket that is owned by account `444455556666`.
@@ -270 +270 @@ The following example bucket policy, in the data owner's account, grants the clu
-                    "AWS": "arn:aws:iam::123456789012:role/amzn-analytics-demo-role"
+                    "AWS": "arn:aws:iam::111122223333:role/amzn-analytics-demo-role"
@@ -313 +313 @@ Whichever permissions policy you use, attach it to an IAM role whose trust polic
-                        "aws:SourceAccount": "123456789012"
+                        "aws:SourceAccount": "111122223333"
@@ -316 +316 @@ Whichever permissions policy you use, attach it to an IAM role whose trust polic
-                        "aws:SourceArn": "arn:aws:rds:us-east-1:123456789012:cluster:amzn-rds-demo-cluster"
+                        "aws:SourceArn": "arn:aws:rds:us-east-1:111122223333:cluster:amzn-rds-demo-cluster"
@@ -327 +327 @@ When you create these IAM policies, follow these best practices:
-  * **Use least privilege** : Grant only the specific Amazon S3 prefixes, AWS Glue resources, and Amazon S3 Tables resources that your foreign tables require. Avoid wildcard (`*`) resource ARNs.
+  * **Use least privilege** – Grant only the specific Amazon S3 prefixes, AWS Glue resources, and Amazon S3 Tables resources that your foreign tables require. Avoid wildcard (`*`) resource ARNs.
@@ -329 +329 @@ When you create these IAM policies, follow these best practices:
-  * **Grant`s3:ListBucket` only where it is needed**: See the summary table for which access paths require it.
+  * **Grant`s3:ListBucket` only where it is needed** – See the summary table for which access paths require it.
@@ -331 +331 @@ When you create these IAM policies, follow these best practices:
-  * **Use prefix conditions** : Apply `s3:prefix` conditions to `s3:ListBucket` actions to restrict which folders can be listed.
+  * **Use prefix conditions** – Apply `s3:prefix` conditions to `s3:ListBucket` actions to restrict which folders can be listed.
@@ -333 +333 @@ When you create these IAM policies, follow these best practices:
-  * **Separate roles for separate concerns** : If different databases or users access different Amazon S3 data, consider using separate IAM roles for each scope.
+  * **Separate roles for separate concerns** – If different databases or users access different Amazon S3 data, consider using separate IAM roles for each scope.
@@ -335 +335 @@ When you create these IAM policies, follow these best practices:
-  * **Audit regularly** : Review policy permissions periodically to confirm that they match your current foreign table definitions.
+  * **Audit regularly** – Review policy permissions periodically to confirm that they match your current foreign table definitions.