AWS Security ChangesHomeSearch

AWS redshift: Redshift federated permissions example prerequisite reworded

Service: redshift · 2026-11-04 · Documentation low

File: redshift/latest/dg/federated-permissions-end-examples.md

Summary

Prerequisite statement in the federated permissions examples now says the producer warehouse is registered with 'Amazon Redshift federated permissions' instead of 'AWS Glue Data Catalog'.

Security assessment

The change is a terminology update to the product name used for the registration step; no security behavior, permission, or vulnerability is described.

Evidence

+The examples assume that the below "IAMR:role_name" roles are already present in the account, if not please create them. Moreover, the producer warehouse is registered with Amazon Redshift federated permissions with name "catalog_name" and has a database of "db_name".

Diff

diff --git a/redshift/latest/dg/federated-permissions-end-examples.md b/redshift/latest/dg/federated-permissions-end-examples.md
index 1138f84..305cc6e 100644
--- a//redshift/latest/dg/federated-permissions-end-examples.md
+++ b//redshift/latest/dg/federated-permissions-end-examples.md
@@ -19 +19 @@ You must be a `superuser` or have the [sys:secadmin](https://docs.aws.amazon.com
-The examples assume that the below "IAMR:role_name" roles are already present in the account, if not please create them. Moreover, the Redshift data warehouse is registered with AWS Glue Data Catalog with name "catalog_name" and has a database of "db_name".
+The examples assume that the below "IAMR:role_name" roles are already present in the account, if not please create them. Moreover, the producer warehouse is registered with Amazon Redshift federated permissions with name "catalog_name" and has a database of "db_name".