AWS managedservices documentation change
Summary
Updated change type from 'review required' to 'managed automation' for Prometheus access requests
Security assessment
Process automation change for IAM role provisioning doesn't indicate security fixes. Maintains existing role security posture.
Diff
diff --git a/managedservices/latest/onboardingguide/pro.md b/managedservices/latest/onboardingguide/pro.md index 2822310bb..a854fbea0 100644 --- a//managedservices/latest/onboardingguide/pro.md +++ b//managedservices/latest/onboardingguide/pro.md @@ -19 +19 @@ Common questions and answers: -Request access by submitting a Management | AWS service | Self-provisioned service | Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: `customer-prometheus-console-role`. After it's provisioned in your account, you must onboard the `customer-prometheus-console-role` role in your federation solution. +Request access by submitting a Management | AWS service | Self-provisioned service | Add (managed automation) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: `customer-prometheus-console-role`. After it's provisioned in your account, you must onboard the `customer-prometheus-console-role` role in your federation solution.