AWS pinpoint documentation change
Summary
Updated Lambda IAM policy examples with concrete account ID (111122223333) and region (us-east-1) in resource ARNs. Added JSON section markers.
Security assessment
Changes provide specific implementation examples rather than addressing security flaws. While proper ARN formatting helps prevent misconfiguration risks, there's no indication this corrects an existing vulnerability.
Diff
diff --git a/pinpoint/latest/userguide/tutorials-two-way-sms-part-2.md b/pinpoint/latest/userguide/tutorials-two-way-sms-part-2.md index 5f064c267..6fa6d917c 100644 --- a//pinpoint/latest/userguide/tutorials-two-way-sms-part-2.md +++ b//pinpoint/latest/userguide/tutorials-two-way-sms-part-2.md @@ -40,0 +41,6 @@ In this tutorial, you want to give Lambda the ability to perform these tasks. Ho +JSON + + +**** + + @@ -56 +62 @@ In this tutorial, you want to give Lambda the ability to perform these tasks. Ho - "Resource": "arn:aws:mobiletargeting:region:accountId:apps/projectId/*" + "Resource": "arn:aws:mobiletargeting:us-east-1:111122223333:apps/projectId/*" @@ -65 +71 @@ In this tutorial, you want to give Lambda the ability to perform these tasks. Ho - "Resource": "arn:aws:mobiletargeting:region:accountId:apps/projectId/endpoints/*" + "Resource": "arn:aws:mobiletargeting:us-east-1:111122223333:apps/projectId/endpoints/*" @@ -70 +76 @@ In this tutorial, you want to give Lambda the ability to perform these tasks. Ho - "Resource": "arn:aws:mobiletargeting:region:accountId:phone/number/validate" + "Resource": "arn:aws:mobiletargeting:us-east-1:111122223333:phone/number/validate"