AWS Security ChangesHomeSearch

AWS AmazonRDS: Formatting of IAM and VPC networking recommendations for Aurora analytics

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

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

Summary

Bullet separators changed from colon to en dash and the introductory sentence now ends with a colon. The underlying recommendations (least-privilege IAM scoped to specific S3 prefixes and Glue table ARNs, same-Region S3 bucket placement, and use of S3 gateway/AWS Glue interface VPC endpoints over NAT gateways) are unchanged in substance.

Security assessment

The changed line documents least-privilege IAM permissions (scoping s3:GetObject/s3:ListBucket and glue:GetTable to specific prefixes and ARNs) plus network-path hardening via VPC endpoints, i.e., security best-practice guidance; however, the edit itself is only a punctuation/style change, not a fix for a specific vulnerability or incident.

Evidence

+  * **Least-privilege IAM** – Grant only `s3:ListBucket` and `s3:GetObject`. Scope these to specific Amazon S3 prefixes using `Condition` blocks. For AWS Glue, grant `glue:GetTable` on specific catalog, database, and table ARNs only.

Diff

diff --git a/AmazonRDS/latest/AuroraUserGuide/aurora-analytics-iam-networking.md b/AmazonRDS/latest/AuroraUserGuide/aurora-analytics-iam-networking.md
index 6b258e1..f7ad17a 100644
--- a//AmazonRDS/latest/AuroraUserGuide/aurora-analytics-iam-networking.md
+++ b//AmazonRDS/latest/AuroraUserGuide/aurora-analytics-iam-networking.md
@@ -9 +9 @@
-The following recommendations apply to the IAM role and VPC networking that you configure when you set up Aurora PostgreSQL analytics.
+The following recommendations apply to the IAM role and VPC networking that you configure when you set up Aurora PostgreSQL analytics:
@@ -11 +11 @@ The following recommendations apply to the IAM role and VPC networking that you
-  * **Least-privilege IAM** : Grant only `s3:ListBucket` and `s3:GetObject`. Scope these to specific Amazon S3 prefixes using `Condition` blocks. For AWS Glue, grant `glue:GetTable` on specific catalog, database, and table ARNs only.
+  * **Least-privilege IAM** – Grant only `s3:ListBucket` and `s3:GetObject`. Scope these to specific Amazon S3 prefixes using `Condition` blocks. For AWS Glue, grant `glue:GetTable` on specific catalog, database, and table ARNs only.
@@ -13 +13 @@ The following recommendations apply to the IAM role and VPC networking that you
-  * **Same-Region Amazon S3 bucket placement** : Place your Amazon S3 data bucket in the same AWS Region as your Aurora DB cluster. Cross-Region reads add latency and data transfer costs.
+  * **Same-Region Amazon S3 bucket placement** – Place your Amazon S3 data bucket in the same AWS Region as your Aurora DB cluster. Cross-Region reads add latency and data transfer costs.
@@ -15 +15 @@ The following recommendations apply to the IAM role and VPC networking that you
-  * **VPC endpoints** : When your DB cluster runs in a private subnet, it can reach Amazon S3 and AWS Glue through either VPC endpoints or a NAT gateway. We recommend VPC endpoints (an Amazon S3 gateway endpoint, plus an AWS Glue interface endpoint for Iceberg) because they keep traffic on the AWS network and the Amazon S3 gateway endpoint adds no hourly charge.
+  * **VPC endpoints** – When your DB cluster runs in a private subnet, it can reach Amazon S3 and AWS Glue through either VPC endpoints or a NAT gateway. We recommend VPC endpoints (an Amazon S3 gateway endpoint, plus an AWS Glue interface endpoint for Iceberg) because they keep traffic on the AWS network and the Amazon S3 gateway endpoint adds no hourly charge.