AWS deadline-cloud high security documentation change
Summary
Corrected service name in ARN example from 'awsdeadlinecloud' to 'deadline' for confused deputy prevention
Security assessment
Fixes an incorrect ARN format example used for cross-service confused deputy prevention. Incorrect ARNs could lead to security misconfigurations in IAM policies. This directly addresses a potential security configuration issue.
Diff
diff --git a/deadline-cloud/latest/developerguide/cross-service-confused-deputy-prevention.md b/deadline-cloud/latest/developerguide/cross-service-confused-deputy-prevention.md index f7e62c7f6..4b0c5e5df 100644 --- a//deadline-cloud/latest/developerguide/cross-service-confused-deputy-prevention.md +++ b//deadline-cloud/latest/developerguide/cross-service-confused-deputy-prevention.md @@ -11 +11 @@ We recommend using the [aws:SourceArn](https://docs.aws.amazon.com/IAM/latest/Us -The most effective way to protect against the confused deputy problem is to use the `aws:SourceArn` global condition context key with the full Amazon Resource Name (ARN) of the resource. If you don't know the full ARN of the resource or if you are specifying multiple resources, use the `aws:SourceArn` global context condition key with wildcard characters (`*`) for the unknown portions of the ARN. For example, `arn:aws:awsdeadlinecloud:*:`123456789012`:*`. +The most effective way to protect against the confused deputy problem is to use the `aws:SourceArn` global condition context key with the full Amazon Resource Name (ARN) of the resource. If you don't know the full ARN of the resource or if you are specifying multiple resources, use the `aws:SourceArn` global context condition key with wildcard characters (`*`) for the unknown portions of the ARN. For example, `arn:aws:deadline:*:`123456789012`:*`.