AWS managedservices documentation change
Summary
Updated AppRegistry access request to use 'managed automation' change type
Security assessment
Process change for IAM role provisioning without security context. No evidence of vulnerability remediation.
Diff
diff --git a/managedservices/latest/onboardingguide/service-catalog-appregistry.md b/managedservices/latest/onboardingguide/service-catalog-appregistry.md index 55ab66d7d..9b7cbc725 100644 --- a//managedservices/latest/onboardingguide/service-catalog-appregistry.md +++ b//managedservices/latest/onboardingguide/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.