AWS application-discovery documentation change
Summary
Added JSON code block markers and section dividers in IAM policy examples
Security assessment
Changes appear to be formatting improvements for existing IAM policy documentation without introducing new security content or addressing vulnerabilities
Diff
diff --git a/application-discovery/latest/userguide/security_iam_id-based-policy-examples.md b/application-discovery/latest/userguide/security_iam_id-based-policy-examples.md index fd83ec60f..5e8c68444 100644 --- a//application-discovery/latest/userguide/security_iam_id-based-policy-examples.md +++ b//application-discovery/latest/userguide/security_iam_id-based-policy-examples.md @@ -56,0 +57,6 @@ An IAM user with this policy attached to their account can configure Application +JSON + + +**** + + @@ -88,0 +96,6 @@ This policy also grants the user access to Arsenal. Arsenal is an agent service +JSON + + +**** + + @@ -112,0 +127,6 @@ For information about using this policy, see [AWS managed policies for AWS Appli +JSON + + +**** + + @@ -197,0 +219,6 @@ The AWSDiscoveryContinuousExportFirehosePolicy policy is required to use data ex +JSON + + +**** + + @@ -252,0 +281,6 @@ The following example shows how to use the `discovery:GetNetworkConnectionGraph` +JSON + + +**** + +