AWS managedservices documentation change
Summary
Modified CloudEndure access request workflow to use managed automation for IAM user provisioning
Security assessment
While credentials are stored in Secrets Manager (existing security practice), the change only affects the approval process automation without introducing new security features or addressing vulnerabilities.
Diff
diff --git a/managedservices/latest/userguide/cloud-endure.md b/managedservices/latest/userguide/cloud-endure.md index 418af44aa..f95b2a566 100644 --- a//managedservices/latest/userguide/cloud-endure.md +++ b//managedservices/latest/userguide/cloud-endure.md @@ -21 +21 @@ Use AMS Self-Service Provisioning (SSP) mode to access AWS CloudEndure capabilit -Request access by submitting a Management | AWS service | Self-provisioned service | Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM User to your account: `customer_cloud_endure_user`. After it's provisioned in your account, the access key and secret key for the user is shared in AWS Secrets Manager. +Request access by submitting a Management | AWS service | Self-provisioned service | Add (managed automation) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM User to your account: `customer_cloud_endure_user`. After it's provisioned in your account, the access key and secret key for the user is shared in AWS Secrets Manager.