AWS Security ChangesHomeSearch

AWS glue medium security documentation change

Service: glue · 2025-11-07 · Security-related medium

File: glue/latest/dg/schema-registry-gs.md

Summary

Removed detailed IAM policy examples for serializers/deserializers and PrivateLink connectivity documentation. Added new sections for integrations and migration.

Security assessment

The removal of IAM policy examples directly impacts security documentation by eliminating guidance on least-privilege permissions for schema registry operations. This could lead to misconfigurations if users no longer have reference policies for secure access control. The deleted IAM examples were concrete security-related configurations.

Diff

diff --git a/glue/latest/dg/schema-registry-gs.md b/glue/latest/dg/schema-registry-gs.md
index fa23c7d04..26f12c2d4 100644
--- a//glue/latest/dg/schema-registry-gs.md
+++ b//glue/latest/dg/schema-registry-gs.md
@@ -5,2 +4,0 @@
-IAM examples for serializersIAM examples for deserializersPrivate connectivity using AWS PrivateLink
-
@@ -15,71 +13 @@ The following sections provide an overview and walk you through setting up and u
-  * [Creating a registry](./schema-registry-gs3.html)
-
-  * [Creating a schema](./schema-registry-gs4.html)
-
-  * [Updating a schema or registry](./schema-registry-gs5.html)
-
-  * [Deleting a schema or registry](./schema-registry-gs7.html)
-
-  * IAM examples for serializers
-
-  * IAM examples for deserializers
-
-  * Private connectivity using AWS PrivateLink
-
-  * [Accessing Amazon CloudWatch metrics](./schema-registry-gs-monitoring.html)
-
-  * [Sample AWS CloudFormation template for schema registry](./schema-registry-integrations-cfn.html)
-
-
-
-
-## IAM examples for serializers
-
-###### Note
-
-AWS managed policies grant necessary permissions for common use cases. For information on using managed policies to manage the schema registry, see [AWS managed (predefined) policies for AWS Glue](./security-iam-awsmanpol.html#access-policy-examples-aws-managed). 
-
-For serializers, you should create a minimal policy similar to that below to give you the ability to find the `schemaVersionId` for a given schema definition. Note, you should have read permissions on the registry in order to read the schemas in the registry. You can limit the registries that can be read by using the `Resource` clause.
-
-Code example 13:
-    
-    
-    {
-        "Sid" : "GetSchemaByDefinition",
-        "Effect" : "Allow",
-        "Action" : 
-    	[
-            "glue:GetSchemaByDefinition"
-        ],
-            "Resource" : ["arn:aws:glue:us-east-2:012345678:registry/registryname-1",
-                          "arn:aws:glue:us-east-2:012345678:schema/registryname-1/schemaname-1",
-                          "arn:aws:glue:us-east-2:012345678:schema/registryname-1/schemaname-2"
-                         ]  
-    }
-
-Further, you can also allow producers to create new schemas and versions by including the following extra methods. Note, you should be able to inspect the registry in order to add/remove/evolve the schemas inside it. You can limit the registries that can be inspected by using the `Resource` clause.
-
-Code example 14:
-    
-    
-    {
-        "Sid" : "RegisterSchemaWithMetadata",
-        "Effect" : "Allow",
-        "Action" : 
-    	[
-            "glue:GetSchemaByDefinition",
-            "glue:CreateSchema",
-            "glue:RegisterSchemaVersion",
-            "glue:PutSchemaVersionMetadata",
-        ],
-        "Resource" : ["arn:aws:glue:aws-region:123456789012:registry/registryname-1",
-                      "arn:aws:glue:aws-region:123456789012:schema/registryname-1/schemaname-1",
-                      "arn:aws:glue:aws-region:123456789012:schema/registryname-1/schemaname-2"
-                     ]  
-    }
-
-## IAM examples for deserializers
-
-For deserializers (consumer side), you should create a policy similar to that below to allow the deserializer to fetch the schema from the Schema Registry for deserialization. Note, you should be able to inspect the registry in order to fetch the schemas inside it.
-
-Code example 15:
+  * [Integrating with AWS Glue Schema Registry](./schema-registry-integrations.html)
@@ -86,0 +15 @@ Code example 15:
+  * [Migration from a third-party schema registry to AWS Glue Schema Registry](./schema-registry-integrations-migration.html)
@@ -88,9 +16,0 @@ Code example 15:
-    {
-        "Sid" : "GetSchemaVersion",
-        "Effect" : "Allow",
-        "Action" : 
-    	[
-            "glue:GetSchemaVersion"
-        ],
-        "Resource" : ["*"]  
-    }
@@ -98 +17,0 @@ Code example 15:
-## Private connectivity using AWS PrivateLink
@@ -100 +18,0 @@ Code example 15:
-You can use AWS PrivateLink to connect your data producer’s VPC to AWS Glue by defining an interface VPC endpoint for AWS Glue. When you use a VPC interface endpoint, communication between your VPC and AWS Glue is conducted entirely within the AWS network. For more information, see [Using AWS Glue with VPC Endpoints](https://docs.aws.amazon.com/glue/latest/dg/vpc-endpoint.html).