AWS deadline-cloud documentation change
Summary
Updated example ARN to use 'deadline' service name instead of 'awsdeadlinecloud'
Security assessment
Corrects an example ARN for confused deputy prevention but does not address a security vulnerability or add new security guidance.
Diff
diff --git a/deadline-cloud/latest/userguide/cross-service-confused-deputy-prevention.md b/deadline-cloud/latest/userguide/cross-service-confused-deputy-prevention.md index b0d52076b..59d05dc1c 100644 --- a//deadline-cloud/latest/userguide/cross-service-confused-deputy-prevention.md +++ b//deadline-cloud/latest/userguide/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`:*`.