AWS redshift: Redshift Data API: isolate access when sharing one IAM role
Summary
Adds a note explaining that when a single IAM role is shared, each user should assume it with a distinct RoleSessionName and access should be scoped with the redshift-data:statement-owner-iam-userid and redshift-data:session-owner-iam-userid condition keys, warning that the RedshiftDbUser session tag is not an isolation control.
Security assessment
The added note documents an IAM isolation best practice: using distinct role session names plus the statement-owner/session-owner condition keys to prevent one shared-role user from acting on another user's Data API statements, and explicitly warns that the RedshiftDbUser session tag must not be relied on for isolation. This is security guidance rather than a fix for a specific disclosed vulnerability.
Evidence
+To isolate access when you share a single IAM role, have each person assume the role with a distinct role session name (`RoleSessionName`). Then scope access with the `redshift-data:statement-owner-iam-userid` and `redshift-data:session-owner-iam-userid` condition keys. The `RedshiftDbUser` session tag is not an isolation control. For more information, see [Configuring IAM permissions](./data-api-iam.html).
Diff
diff --git a/redshift/latest/mgmt/data-api.md b/redshift/latest/mgmt/data-api.md index 0818c49..2b9d68f 100644 --- a//redshift/latest/mgmt/data-api.md +++ b//redshift/latest/mgmt/data-api.md @@ -102,0 +103,4 @@ By default in AWS Step Functions, retries are not enabled. If you need to call a +###### Note + +To isolate access when you share a single IAM role, have each person assume the role with a distinct role session name (`RoleSessionName`). Then scope access with the `redshift-data:statement-owner-iam-userid` and `redshift-data:session-owner-iam-userid` condition keys. The `RedshiftDbUser` session tag is not an isolation control. For more information, see [Configuring IAM permissions](./data-api-iam.html). +