AWS forecast high security documentation change
Summary
Removed IAM role trust policy and KMS policy examples
Security assessment
The removed trust policy included critical security conditions (e.g., SourceAccount, SourceArn) to restrict role assumptions. Removing these examples could lead to overly permissive roles, increasing the risk of unauthorized access. This change directly impacts secure IAM configuration guidance.
Diff
diff --git a/forecast/latest/dg/aws-forecast-iam-roles.md b/forecast/latest/dg/aws-forecast-iam-roles.md index e094e930b..c182e9a0d 100644 --- a//forecast/latest/dg/aws-forecast-iam-roles.md +++ b//forecast/latest/dg/aws-forecast-iam-roles.md @@ -56,0 +57,6 @@ You can use the AWS IAM console to do the following: +JSON + + +**** + + @@ -101,22 +107,0 @@ Click **Next**. - { - "Version": "2012-10-17", - "Statement": [ - { - "Sid": "", - "Effect": "Allow", - "Principal": { - "Service": "forecast.amazonaws.com" - }, - "Action": "sts:AssumeRole", - "Condition": { - "StringEquals": { - "aws:SourceAccount": "account-id" - }, - "ArnLike": { - "aws:SourceArn": "arn:aws:forecast:region:account-id:*" - } - } - } - ] - } - @@ -125,12 +109,0 @@ Click **Next**. - { - "Version": "2012-10-17", - "Statement": [ - { - "Sid": "ForecastKMS", - "Effect": "Allow", - "Action": "kms:*", - "Resource": "arn:aws:kms:region:account-id:key/KMS-key-id" - } - ] - } -