AWS pinpoint documentation change
Summary
Added JSON code block markers, updated ARNs to use specific region/account ID (us-east-1/111122223333), and removed example role output.
Security assessment
Standardization of example ARNs to use placeholder account IDs improves documentation clarity but does not address security vulnerabilities. Removal of verbose examples is editorial.
Diff
diff --git a/pinpoint/latest/archguide/permissions-get-recommendations.md b/pinpoint/latest/archguide/permissions-get-recommendations.md index 72a451204..7ce9404e3 100644 --- a//pinpoint/latest/archguide/permissions-get-recommendations.md +++ b//pinpoint/latest/archguide/permissions-get-recommendations.md @@ -46,0 +47,6 @@ In the following procedure, the example policy allows this access for a particul +JSON + + +**** + + @@ -59,2 +65,2 @@ In the following procedure, the example policy allows this access for a particul - "arn:aws:personalize:region:accountId:solution/solutionId", - "arn:aws:personalize:region:accountId:campaign/campaignId" + "arn:aws:personalize:us-east-1:111122223333:solution/solutionId", + "arn:aws:personalize:us-east-1:111122223333:campaign/campaignId" @@ -119,0 +127,6 @@ Each IAM role contains a _trust policy_ , which is a set of rules that specifies +JSON + + +**** + + @@ -143,22 +156,0 @@ If the command runs successfully, you will see an output similar to the followin - { - "Role": { - "Path": "/", - "RoleName": "PinpointRoleforPersonalize", - "RoleId": "AKIAIOSFODNN7EXAMPLE", - "Arn": "arn:aws:iam::123456789012:role/PinpointRoleforPersonalize", - "CreateDate": "2020-03-04T22:29:45Z", - "AssumeRolePolicyDocument": { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Principal": { - "Service": "pinpoint.amazonaws.com" - }, - "Action": "sts:AssumeRole" - } - ] - } - } - } -