AWS managedservices documentation change
Summary
Updated Compute Optimizer access request to use 'managed automation' process
Security assessment
Process change for service provisioning without security implications. Maintains same IAM role configuration without security enhancements.
Diff
diff --git a/managedservices/latest/onboardingguide/compute-optimizer.md b/managedservices/latest/onboardingguide/compute-optimizer.md index 9233cbd16..ae16ae442 100644 --- a//managedservices/latest/onboardingguide/compute-optimizer.md +++ b//managedservices/latest/onboardingguide/compute-optimizer.md @@ -15 +15 @@ Use AMS Self-Service Provisioning (SSP) mode to access AWS Compute Optimizer cap -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_compute_optimizer_readonly_role`. After it's provisioned in your account, you must onboard the 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_compute_optimizer_readonly_role`. After it's provisioned in your account, you must onboard the role in your federation solution.