AWS managedservices documentation change
Summary
Updated change type from 'review required' to 'managed automation' for Prometheus access
Security assessment
The change modifies the provisioning workflow but maintains the same IAM role requirements. No security-related justification or vulnerability mitigation is provided.
Diff
diff --git a/managedservices/latest/userguide/pro.md b/managedservices/latest/userguide/pro.md index d9615e498..e2c3a4e85 100644 --- a//managedservices/latest/userguide/pro.md +++ b//managedservices/latest/userguide/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.