AWS managedservices documentation change
Summary
Changed RFC process to 'managed automation' for CloudEndure user provisioning
Security assessment
While the change affects how IAM user credentials are provisioned (now via managed automation), there is no indication of fixing a security issue or adding security safeguards. Credential storage in Secrets Manager was already part of the process.
Diff
diff --git a/managedservices/latest/onboardingguide/cloud-endure.md b/managedservices/latest/onboardingguide/cloud-endure.md index 2dd2b2478..77223796d 100644 --- a//managedservices/latest/onboardingguide/cloud-endure.md +++ b//managedservices/latest/onboardingguide/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.