AWS Security ChangesHomeSearch

AWS AmazonRDS: Aurora analytics prerequisites: IAM privilege table and example cleanup

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

File: AmazonRDS/latest/AuroraUserGuide/aurora-analytics-prerequisites.md · Type: iam

Summary

Replaces placeholder account IDs (123456789012 → 111122223333) and bucket names (amzn-s3-demo-bucket), fixes the IAM privileges table header, and reformats CLI command examples for adding the IAM role and modifying the cluster parameter group. No new security guidance is introduced.

Security assessment

The change only swaps example account IDs/bucket names and fixes table/command formatting in an existing IAM-privileges table; the least-privilege content itself is unchanged, so there is no new or fixed security control.

Evidence

AWS Glue Data Catalog (`arn:aws:glue:us-east-1:111122223333:table/mydb/mytable`) | `glue:GetTable` \+ Amazon S3 privileges above

Diff

diff --git a/AmazonRDS/latest/AuroraUserGuide/aurora-analytics-prerequisites.md b/AmazonRDS/latest/AuroraUserGuide/aurora-analytics-prerequisites.md
index 1867d7f..4315c94 100644
--- a//AmazonRDS/latest/AuroraUserGuide/aurora-analytics-prerequisites.md
+++ b//AmazonRDS/latest/AuroraUserGuide/aurora-analytics-prerequisites.md
@@ -53 +53 @@ Create an IAM policy that grants the extension read access to Amazon S3, and opt
-The minimum privileges depend on how you reference the data: the data format (Parquet or Iceberg), the source (Amazon S3, AWS Glue Data Catalog, or Amazon S3 Tables), and whether you point at a single file or a directory. The following table lists the minimum IAM role privileges for the common same-account scenarios:
+The minimum privileges depend on how you reference the data: the data format (Parquet or Iceberg), the source (Amazon S3, AWS Glue Data Catalog, or Amazon S3 Tables), and whether you point at a single file or a directory. The following table lists the minimum IAM role privileges for the common same-account scenarios.
@@ -55 +55 @@ The minimum privileges depend on how you reference the data: the data format (Pa
-Minimum IAM role privileges by source Source | Minimum privileges  
+Source | Minimum privileges  
@@ -59,3 +59,3 @@ Amazon S3, directory or glob (`s3://bucket/path/`) | `s3:GetObject`, `s3:ListBuc
-AWS Glue Data Catalog (`arn:aws:glue:us-east-1:123456789012:table/mydb/mytable`) | `glue:GetTable` \+ Amazon S3 privileges above  
-Amazon S3 Tables, direct ARN (`arn:aws:s3tables:us-east-1:123456789012:bucket/mybucket/table/table_id`) | `s3tables:GetTable`, `s3tables:GetTableBucket`, `s3tables:GetTableData`, `s3tables:GetNamespace`  
-Amazon S3 Tables, via AWS Glue catalog ARN (`arn:aws:glue:us-east-1:123456789012:table/s3tablescatalog/mybucket/myns/mytable`) | `glue:GetTable` \+ `s3tables` privileges above  
+AWS Glue Data Catalog (`arn:aws:glue:us-east-1:111122223333:table/mydb/mytable`) | `glue:GetTable` \+ Amazon S3 privileges above  
+Amazon S3 Tables, direct ARN (`arn:aws:s3tables:us-east-1:111122223333:bucket/amzn-s3-demo-bucket/table/table_id`) | `s3tables:GetTable`, `s3tables:GetTableBucket`, `s3tables:GetTableData`, `s3tables:GetNamespace`  
+Amazon S3 Tables, through the AWS Glue catalog ARN (`arn:aws:glue:us-east-1:111122223333:table/s3tablescatalog/amzn-s3-demo-bucket/myns/mytable`) | `glue:GetTable` \+ `s3tables` privileges above  
@@ -129 +129 @@ Create an IAM role that Aurora can assume to access your Amazon S3 data on behal
-      --policy-arn arn:aws:iam::123456789012:policy/AuroraAnalyticsReadAccess
+      --policy-arn arn:aws:iam::111122223333:policy/AuroraAnalyticsReadAccess
@@ -157 +157,3 @@ After you create the DB cluster, associate the IAM role that you created for the
-  *     aws rds add-role-to-db-cluster \
+  * Run the following command.
+    
+        aws rds add-role-to-db-cluster \
@@ -161 +163 @@ After you create the DB cluster, associate the IAM role that you created for the
-      --role-arn arn:aws:iam::123456789012:role/AuroraAnalyticsRole
+      --role-arn arn:aws:iam::111122223333:role/AuroraAnalyticsRole
@@ -166 +168 @@ After you create the DB cluster, associate the IAM role that you created for the
-The IAM role status shows as **Active** after it is successfully attached. For more information, see [add-role-to-db-cluster](https://docs.aws.amazon.com/cli/latest/reference/rds/add-role-to-db-cluster.html) in the _AWS CLI Command Reference_.
+After you attach the role, the IAM role status shows as `Active`. This might take a few minutes. For more information, see [add-role-to-db-cluster](https://docs.aws.amazon.com/cli/latest/reference/rds/add-role-to-db-cluster.html) in the _AWS CLI Command Reference_.
@@ -174 +176,3 @@ VPC endpoints keep traffic on the AWS network without traversing the public inte
-Required VPC endpoints Service | Endpoint type | Required for  
+The following table lists the required VPC endpoints.
+
+Service | Endpoint type | Required for  
@@ -206 +210,3 @@ The `aurora_analytics.enabled` parameter is set to `false` by default. After you
-  *     aws rds modify-db-cluster-parameter-group \
+  * Run the following command.
+    
+        aws rds modify-db-cluster-parameter-group \