AWS managedservices documentation change
Summary
Modified Textract access request process to use 'managed automation' instead of manual review
Security assessment
Process change for service provisioning automation without security-specific enhancements. The roles being provisioned (customer_textract_console_role etc.) remain unchanged in their permissions.
Diff
diff --git a/managedservices/latest/userguide/textract.md b/managedservices/latest/userguide/textract.md index eb3ea2fba..a05f24321 100644 --- a//managedservices/latest/userguide/textract.md +++ b//managedservices/latest/userguide/textract.md @@ -17 +17 @@ Common questions and answers: -Request access by submitting a Management | AWS service | Self-provisioned service | Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM roles to your account: `customer_textract_console_role`, `customer_textract_human_review_execution_role`, and `customer_ec2_textract_instance_profile`. Once provisioned in your account, you must onboard the role `customer_textract_console_role` in your federation solution. +Request access by submitting a Management | AWS service | Self-provisioned service | Add (managed automation) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM roles to your account: `customer_textract_console_role`, `customer_textract_human_review_execution_role`, and `customer_ec2_textract_instance_profile`. Once provisioned in your account, you must onboard the role `customer_textract_console_role` in your federation solution.