AWS pinpoint documentation change
Summary
Added JSON code block markers and removed example IAM role creation output. Updated formatting with section breaks (****).
Security assessment
Changes involve formatting improvements (adding JSON markers/section breaks) and removing verbose CLI output examples. No evidence of addressing vulnerabilities or security features.
Diff
diff --git a/pinpoint/latest/archguide/permissions-export-endpoints.md b/pinpoint/latest/archguide/permissions-export-endpoints.md index f3a817d74..f51317e6d 100644 --- a//pinpoint/latest/archguide/permissions-export-endpoints.md +++ b//pinpoint/latest/archguide/permissions-export-endpoints.md @@ -33,0 +34,6 @@ An IAM policy defines the permissions for an entity, such as an identity or reso +JSON + + +**** + + @@ -127,0 +135,6 @@ Now that you've created an IAM policy, you can create a role and attach the poli +JSON + + +**** + + @@ -149,22 +162,0 @@ If the command runs successfully, you will see an output similar to the followin - { - "Role": { - "RoleName": "s3ExportRole", - "AssumeRolePolicyDocument": { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Principal": { - "Service": "pinpoint.amazonaws.com" - }, - "Action": "sts:AssumeRole" - } - ] - }, - "RoleId": "AROAICPO353GIPEXAMPLE", - "Arn": "arn:aws:iam::123456789012:role/s3ExportRole", - "CreateDate": "2018-04-11T18:52:36.712Z", - "Path": "/" - } - } -