AWS iotevents documentation change
Summary
Added JSON formatting markers and updated example policy with concrete account ID (123456789012) and region (us-east-1)
Security assessment
The change improves IAM policy examples but doesn't address a specific vulnerability. Updates to concrete values help prevent accidental use of placeholder values in real policies.
Diff
diff --git a/iotevents/latest/developerguide/accessing-a-detector-model.md b/iotevents/latest/developerguide/accessing-a-detector-model.md index 4e05164c7..e9846486c 100644 --- a//iotevents/latest/developerguide/accessing-a-detector-model.md +++ b//iotevents/latest/developerguide/accessing-a-detector-model.md @@ -10,0 +11,6 @@ This example demonstrates how to create an IAM policy that securely grants acces +JSON + + +**** + + @@ -25 +31 @@ This example demonstrates how to create an IAM policy that securely grants acces - "aws:SourceAccount": "account_id" + "aws:SourceAccount": "123456789012" @@ -28 +34 @@ This example demonstrates how to create an IAM policy that securely grants acces - "aws:SourceArn": "arn:aws:iotevents:region:account_id:detectorModel/WindTurbine01" + "aws:SourceArn": "arn:aws:iotevents:us-east-1:123456789012:detectorModel/WindTurbine01"