AWS connect documentation change
Summary
Added JSON section markers and formatting dividers (****) in multiple IAM policy examples
Security assessment
Structural formatting changes to existing policy examples without modifying security permissions or adding new security guidance.
Diff
diff --git a/connect/latest/adminguide/security_iam_id-based-policy-examples.md b/connect/latest/adminguide/security_iam_id-based-policy-examples.md index 1928216c7..afd60c7eb 100644 --- a//connect/latest/adminguide/security_iam_id-based-policy-examples.md +++ b//connect/latest/adminguide/security_iam_id-based-policy-examples.md @@ -98,0 +99,6 @@ For example, imagine you have a group of entry-level developers. You can create +JSON + + +**** + + @@ -123,0 +131,6 @@ This example shows how you might create a policy that allows users to interact w +JSON + + +**** + + @@ -155,0 +170,6 @@ The following sample policy allows the "describe" and "update" actions for users +JSON + + +**** + + @@ -181,0 +203,6 @@ The following sample policy allows the create actions for users with specific re +JSON + + +**** + + @@ -207,0 +236,6 @@ The following sample policy allows event integrations to be created, listed, and +JSON + + +**** + + @@ -228,0 +264,6 @@ The following sample policy allows Amazon Q in Connect assistants to be created, +JSON + + +**** + + @@ -319,0 +362,6 @@ To disable outbound campaigns for an instance, add the following permissions: +JSON + + +**** + +