AWS lake-formation documentation change
Summary
Added note clarifying cross-account Redshift catalog ARN input despite console display limitations
Security assessment
The change addresses a UI limitation but does not introduce or modify security features. It clarifies user workflow without security implications.
Diff
diff --git a/lake-formation/latest/dg/catalog-resource-link.md b/lake-formation/latest/dg/catalog-resource-link.md index 61de6b078..0304a1c0a 100644 --- a//lake-formation/latest/dg/catalog-resource-link.md +++ b//lake-formation/latest/dg/catalog-resource-link.md @@ -56,0 +57,6 @@ The list contains all the catalogs shared with your account. Note the catalog ow +###### Note + +When creating a catalog link container through the console, the **Target Redshift Catalog** dropdown might display `No matches` when attempting to select a cross-account Redshift catalog. Despite this display, you can manually enter the target ARN of the Amazon Redshift federated database-level catalog (Amazon Redshift database) in the input field, and the form will still work correctly. For example: `arn:aws:glue:us-east-1:123456789012:catalog/federated-catalog-redshift/dev`. + +This behavior occurs because the console can only search for potential candidates within the currently signed-in account. The dropdown is intended as an auto-complete feature, but you can still manually input ARNs for cross-account access. +