AWS managedservices documentation change
Summary
Changed RFC change type from 'Add (review required)' to 'Add (managed automation)' for AppRegistry access requests
Security assessment
This change modifies the process flow from manual review to automated handling but doesn't explicitly address security vulnerabilities or weaknesses. The security implications of automated provisioning vs manual review are not discussed.
Diff
diff --git a/managedservices/latest/userguide/service-catalog-appregistry.md b/managedservices/latest/userguide/service-catalog-appregistry.md index 9d9c7bdd8..83d54ccc7 100644 --- a//managedservices/latest/userguide/service-catalog-appregistry.md +++ b//managedservices/latest/userguide/service-catalog-appregistry.md @@ -17 +17 @@ With AppRegistry, you can store your AWS applications, the collection of resourc -Request access to AppRegistry by submitting an RFC with the Management | AWS service | Self-provisioned service | Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: `customer-appregistry-console-role`. After provisioned in your account, you must onboard the role in your federation solution. +Request access to AppRegistry by submitting an RFC with the Management | AWS service | Self-provisioned service | Add (managed automation) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: `customer-appregistry-console-role`. After provisioned in your account, you must onboard the role in your federation solution.