AWS Security ChangesHomeSearch

AWS managedservices documentation change

Service: managedservices · 2025-10-25 · Documentation low

File: managedservices/latest/userguide/compute-optimizer.md

Summary

Updated change type to '(managed automation)' for Compute Optimizer access requests

Security assessment

Process automation change with no security controls added or vulnerabilities addressed in documentation.

Diff

diff --git a/managedservices/latest/userguide/compute-optimizer.md b/managedservices/latest/userguide/compute-optimizer.md
index a20f1023f..8cf64c3ed 100644
--- a//managedservices/latest/userguide/compute-optimizer.md
+++ b//managedservices/latest/userguide/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.