AWS Security ChangesHomeSearch

AWS emr documentation change

Service: emr · 2025-08-10 · Documentation low

File: emr/latest/ReleaseGuide/emr-iceberg-use-trino-cluster.md

Summary

Updated configuration method from creating iceberg.properties file to using configurations.json format and removed bootstrap action steps in favor of --configurations parameter

Security assessment

The change modifies configuration methodology but does not address security vulnerabilities or introduce security features. Focuses on procedural improvements rather than security controls.

Diff

diff --git a/emr/latest/ReleaseGuide/emr-iceberg-use-trino-cluster.md b/emr/latest/ReleaseGuide/emr-iceberg-use-trino-cluster.md
index 6fa610373..4f547c100 100644
--- a//emr/latest/ReleaseGuide/emr-iceberg-use-trino-cluster.md
+++ b//emr/latest/ReleaseGuide/emr-iceberg-use-trino-cluster.md
@@ -17 +17 @@ To use Iceberg on Amazon EMR with the AWS CLI, first create a cluster with the f
-  1. Create an `iceberg.properties` file and set a value for your chosen catalog. For example, if you want to use the Hive metastore as your catalog, your file should have the following content.
+  1. Create an `configurations.json` file with the following content. For example, if you want to use the Hive metastore as your catalog, your file should have the following content.
@@ -19,2 +19,9 @@ To use Iceberg on Amazon EMR with the AWS CLI, first create a cluster with the f
-        connector.name=iceberg
-    hive.metastore.uri=thrift://localhost:9083
+        [
+      {
+        "Classification": "trino-connector-iceberg",
+        "Properties": {
+          "connector.name": "iceberg",
+          "hive.metastore.uri": "thrift://localhost:9083"
+        }
+      }
+    ]
@@ -24,7 +31,9 @@ If you want to use the AWS Glue Data Catalog as your store, your file should hav
-        connector.name=iceberg
-    iceberg.catalog.type=glue
-
-  2. Create a bootstrap action that copies `iceberg.properties` from Amazon S3 to `/etc/trino/conf/catalog/iceberg.properties`, as in the following example. For information on bootstrap actions, see [Create bootstrap actions to install additional software](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-bootstrap.html).
-    
-        set -ex
-    sudo aws s3 cp s3://amzn-s3-demo-bucket/iceberg.properties /etc/trino/conf/catalog/iceberg.properties
+        [
+      {
+        "Classification": "trino-connector-iceberg",
+        "Properties": {
+          "connector.name": "iceberg",
+          "iceberg.catalog.type": "glue"
+        }
+      }
+    ]
@@ -32 +41 @@ If you want to use the AWS Glue Data Catalog as your store, your file should hav
-  3. Create a cluster with the following configuration, replacing the example bootstrap actions script path and key name with your own.
+  2. Create a cluster with the following configuration, replacing the example Amazon S3 bucket path and key name with your own.
@@ -38 +47,2 @@ If you want to use the AWS Glue Data Catalog as your store, your file should hav
-    --bootstrap-actions '[{"Path":"s3://amzn-s3-demo-bucket","Name":"Add iceberg.properties"}]' \
+    --log-uri s3://amzn-s3-demo-bucket \
+    --configurations file://configurations.json \
@@ -46,13 +55,0 @@ If you want to use the AWS Glue Data Catalog as your store, your file should hav
-You can add a configuration, which is an optional specification for your cluster, that specifies the following connector configuration properties for _trino-connector-iceberg_ :
-    
-    
-    [
-                  {
-                   "Classification": "trino-connector-iceberg",
-                   "Properties": {
-                                 "connector.name": "iceberg",
-                                 "iceberg.catalog.type": "glue"
-                     }
-                   }
-                   ]
-