AWS Security ChangesHomeSearch

AWS redshift high security documentation change

Service: redshift · 2025-11-16 · Security-related high

File: redshift/latest/mgmt/redshift-iam-access-control-identity-based.md

Summary

Updated IAM policy documentation for GetClusterCredentials with SAML SSO security recommendations, added explicit examples with wildcard warnings, and renamed policy example section

Security assessment

Added explicit guidance for SAML SSO integrations requiring IAM policy conditions to prevent credential misuse (matching aws:userid with redshift:DbUser). Multiple warnings about risks of wildcard permissions in IAM policies address security best practices. These changes directly mitigate potential privilege escalation risks.

Diff

diff --git a/redshift/latest/mgmt/redshift-iam-access-control-identity-based.md b/redshift/latest/mgmt/redshift-iam-access-control-identity-based.md
index 3040cebf2..3d3266c9c 100644
--- a//redshift/latest/mgmt/redshift-iam-access-control-identity-based.md
+++ b//redshift/latest/mgmt/redshift-iam-access-control-identity-based.md
@@ -5 +5 @@
-AWS managed policies for Amazon RedshiftPolicy updatesAmazonRedshiftReadOnlyAccessAmazonRedshiftFullAccessAmazonRedshiftQueryEditorAmazonRedshiftDataFullAccessAmazonRedshiftQueryEditorV2FullAccessAmazonRedshiftQueryEditorV2NoSharingAmazonRedshiftQueryEditorV2ReadSharingAmazonRedshiftQueryEditorV2ReadWriteSharingAmazonRedshiftServiceLinkedRolePolicyAmazonRedshiftAllCommandsFullAccessPermissions required to use Redshift SpectrumPermissions required to use the Amazon Redshift consolePermissions required to use the Amazon Redshift console query editorPermissions required to use the query editor v2 Permissions required to use the Amazon Redshift schedulerPermissions required to use the Amazon EventBridge schedulerPermissions required to use Amazon Redshift machine learning (ML)Permissions for streaming ingestionPermissions required to use the data sharing API operationsResource policies for GetClusterCredentialsCustomer managed policy examplesExample policy for using GetClusterCredentials
+AWS managed policies for Amazon RedshiftPolicy updatesAmazonRedshiftReadOnlyAccessAmazonRedshiftFullAccessAmazonRedshiftQueryEditorAmazonRedshiftDataFullAccessAmazonRedshiftQueryEditorV2FullAccessAmazonRedshiftQueryEditorV2NoSharingAmazonRedshiftQueryEditorV2ReadSharingAmazonRedshiftQueryEditorV2ReadWriteSharingAmazonRedshiftServiceLinkedRolePolicyAmazonRedshiftAllCommandsFullAccessPermissions required to use Redshift SpectrumPermissions required to use the Amazon Redshift consolePermissions required to use the Amazon Redshift console query editorPermissions required to use the query editor v2 Permissions required to use the Amazon Redshift schedulerPermissions required to use the Amazon EventBridge schedulerPermissions required to use Amazon Redshift machine learning (ML)Permissions for streaming ingestionPermissions required to use the data sharing API operationsResource policies for GetClusterCredentialsCustomer managed policy examplesExample 8: IAM policy for using GetClusterCredentials
@@ -1140 +1140 @@ Following is an IAM policy that prevents an entity from calling `AuthorizeDataSh
-To connect to a cluster database using a JDBC or ODBC connection with IAM database credentials, or to programmatically call the `GetClusterCredentials` action, you need a minimum set of permissions. At a minimum, you need permission to call the `redshift:GetClusterCredentials` action with access to a `dbuser` resource.
+To connect to a cluster database using a JDBC or ODBC connection with IAM database credentials, or to programmatically call the `GetClusterCredentials` action, you need permission to call the `redshift:GetClusterCredentials` action with access to a `dbuser` resource.
@@ -1165 +1165,3 @@ You can also include the following conditions in your policy:
-For more information about conditions, see [Specifying conditions in a policy](./redshift-iam-access-control-overview.html#redshift-policy-resources.specifying-conditions). 
+###### Important
+
+For SAML SSO integrations, you may be required to specify an IAM Policy using the `${redshift:DbUser}` variable. In those cases, we strongly recommend the use of a condition statement that ensures a caller cannot obtain credentials for a user which does not match their aws userid. E.g. `"StringEquals": {"aws:userid":"AIDIODR4TAW7CSEXAMPLE:${redshift:DbUser}"}"`. See Example 8: IAM policy for using GetClusterCredentials. For more information about conditions, see [Specifying conditions in a policy](./redshift-iam-access-control-overview.html#redshift-policy-resources.specifying-conditions)
@@ -1500 +1502 @@ JSON
-## Example policy for using GetClusterCredentials
+## Example 8: IAM policy for using GetClusterCredentials
@@ -1570,0 +1573,71 @@ JSON
+The following example shows a policy that allows the IAM role to call the `GetClusterCredentials` operation. Specifying the Amazon Redshift `dbuser` resource grants the role access to the database user name ` temp_creds_user` on the cluster named ` examplecluster`.
+
+JSON
+    
+
+****
+    
+    
+    
+    {
+      "Version":"2012-10-17",		 	 	 
+      "Statement": {
+        "Effect": "Allow",
+        "Action": "redshift:GetClusterCredentials",
+        "Resource": "arn:aws:redshift:us-west-2:123456789012:dbuser:examplecluster/temp_creds_user"
+      }
+    }
+    
+
+You can use a wildcard (*) to replace all, or a portion of, the cluster name, user name, and database group names. The following example allows any user name beginning with `temp_` with any cluster in the specified account.
+
+###### Important
+
+The statement in the following example specifies a wildcard character (*) as part of the value for the resource so that the policy permits any resource that begins with the specified characters. Using a wildcard character in your IAM policies might be overly permissive. As a best practice, we recommend using the most restrictive policy feasible for your business application. 
+
+JSON
+    
+
+****
+    
+    
+    
+    {
+      "Version":"2012-10-17",		 	 	 
+      "Statement": {
+        "Effect": "Allow",
+        "Action": "redshift:GetClusterCredentials",
+        "Resource": "arn:aws:redshift:us-west-2:123456789012:dbuser:*/temp_*"
+      }
+    }
+    
+
+The following example shows a policy that allows the IAM role to call the `GetClusterCredentials` operation with the option to automatically create a new user and specify groups the user joins at login. The `"Resource": "*" `clause grants the role access to any resource, including clusters, database users, or user groups.
+
+###### Important
+
+The statement in the following example specifies a wildcard character (*) as the resource for the given actions, so that the policy permits access to any cluster and database users, and allows creating any user. Using a wildcard character in your IAM policies might be overly permissive. As a best practice, we recommend using the most restrictive policy feasible for your business application. 
+
+JSON
+    
+
+****
+    
+    
+    
+    {
+      "Version":"2012-10-17",		 	 	 
+      "Statement": {
+        "Effect": "Allow",
+        "Action": [
+                 "redshift:GetClusterCredentials",
+                 "redshift:CreateClusterUser",
+    		"redshift:JoinGroup"
+                ],
+        "Resource": "*"
+      }
+    }
+    
+
+For more information, see [Amazon Redshift ARN syntax](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-redshift).
+