AWS managedservices documentation change
Summary
Updated IAM role creation change types to use 'managed automation' instead of 'review required'
Security assessment
Changes relate to process automation for IAM role creation but don't introduce new security controls or address specific vulnerabilities. The security posture remains unchanged as roles are still being provisioned through approved mechanisms.
Diff
diff --git a/managedservices/latest/userguide/setting-permissions.md b/managedservices/latest/userguide/setting-permissions.md index 2e1edc110..c8a4c2286 100644 --- a//managedservices/latest/userguide/setting-permissions.md +++ b//managedservices/latest/userguide/setting-permissions.md @@ -15 +15 @@ AMS uses an IAM role to set user permissions through your federation service and -You can request a custom IAM role with the Deployment | Advanced stack components | Identity and Access Management (IAM) | Create entity or policy (review required) change type (ct-3dpd8mdd9jn1r), or an IAM instance profile with the Management | Applications | IAM instance profile | Create Management | Applications | IAM instance profile | Create (review required) change type (ct-0ixp4ch2tiu04). See the descriptions of each in this section. +You can request a custom IAM role with the Deployment | Advanced stack components | Identity and Access Management (IAM) | Create entity or policy (managed automation) change type (ct-3dpd8mdd9jn1r), or an IAM instance profile with the Management | Applications | IAM instance profile | Create Management | Applications | IAM instance profile | Create (managed automation) change type (ct-0ixp4ch2tiu04). See the descriptions of each in this section.