AWS billingconductor documentation change
Summary
Added JSON examples and formatting to IAM policy examples
Security assessment
The addition of JSON examples improves the documentation of IAM policies, which are security-related, but does not address a specific security issue.
Diff
diff --git a/billingconductor/latest/userguide/security_iam_id-based-policy-examples.md b/billingconductor/latest/userguide/security_iam_id-based-policy-examples.md index b5f707136..67d575f03 100644 --- a//billingconductor/latest/userguide/security_iam_id-based-policy-examples.md +++ b//billingconductor/latest/userguide/security_iam_id-based-policy-examples.md @@ -71,0 +72,6 @@ In addition to the `billingconductor:*` permissions, `pricing:DescribeServices` +JSON + + +**** + + @@ -102,0 +110,6 @@ In this example, you grant an IAM entity full access to the Billing Conductor AP +JSON + + +**** + + @@ -123,0 +138,6 @@ In this example, you grant an IAM entity read-only access to the Billing Conduct +JSON + + +**** + + @@ -149,0 +171,6 @@ In this example, IAM entities can toggle and view pro forma billing data through +JSON + + +**** + + @@ -168,0 +197,6 @@ In this example, IAM entities can toggle and view pro forma billing data through +JSON + + +**** + + @@ -188,0 +224,6 @@ In this example, IAM entities have read-only access to the specific AWS Organiza +JSON + + +**** + + @@ -208,0 +251,6 @@ In this example, IAM entities are denied access to services and features that do +JSON + + +**** + + @@ -281 +330 @@ How AWS Billing Conductor works with IAM -AWS managed policies for Billing Conductor. +AWS managed policies for Billing Conductor