AWS lookout-for-vision documentation change
Summary
Removed KMS key policy example for custom encryption
Security assessment
Removal of a specific KMS policy example but no indication of security vulnerability. Could be documentation cleanup rather than security-related change. No evidence of addressing a security issue.
Diff
diff --git a/lookout-for-vision/latest/developer-guide/su-kms-encryption.md b/lookout-for-vision/latest/developer-guide/su-kms-encryption.md index 8f88c7449..51fe2a0ec 100644 --- a//lookout-for-vision/latest/developer-guide/su-kms-encryption.md +++ b//lookout-for-vision/latest/developer-guide/su-kms-encryption.md @@ -15,27 +14,0 @@ If you want to use your own KMS key, use the following policy to specify the KMS - - { - "Version": "2012-10-17", - "Statement": [ - { - "Sid": "LookoutVisionKmsDescribeAccess", - "Effect": "Allow", - "Action": "kms:DescribeKey", - "Resource": "kms_key_arn" - }, - { - "Sid": "LookoutVisionKmsCreateGrantAccess", - "Effect": "Allow", - "Action": "kms:CreateGrant", - "Resource": "kms_key_arn", - "Condition": { - "StringLike": { - "kms:ViaService": "lookoutvision.*.amazonaws.com" - }, - "Bool": { - "kms:GrantIsForAWSResource": "true" - } - } - } - ] - } -