AWS managedservices documentation change
Summary
Updated IAM role creation process from 'review required' to 'managed automation' change type for AppStream 2.0
Security assessment
Process change for IAM role creation automation without security vulnerability context. Maintains existing security requirements through naming conventions.
Diff
diff --git a/managedservices/latest/onboardingguide/amz-app-stream-2.0.md b/managedservices/latest/onboardingguide/amz-app-stream-2.0.md index efef95730..84e788d0c 100644 --- a//managedservices/latest/onboardingguide/amz-app-stream-2.0.md +++ b//managedservices/latest/onboardingguide/amz-app-stream-2.0.md @@ -54 +54 @@ While submitting the RFC to onboard AppStream 2.0, include the Amazon S3 bucket - * In order to create and choose an IAM role that will be available on all fleet streaming instances, submit a Deployment | Advanced stack components | Identity and Access Management (IAM) | Create entity or policy (review required) change type (ct-3dpd8mdd9jn1r) RFC requesting the IAM role with the required policy. The IAM role name should always start with prefix : "customer_appstream". + * In order to create and choose an IAM role that will be available on all fleet streaming instances, submit a Deployment | Advanced stack components | Identity and Access Management (IAM) | Create entity or policy (managed automation) change type (ct-3dpd8mdd9jn1r) RFC requesting the IAM role with the required policy. The IAM role name should always start with prefix : "customer_appstream".