AWS managedservices documentation change
Summary
Changed multiple instances of 'review required' to 'managed automation' for service access and KMS key creation
Security assessment
While affecting IAM role and KMS key provisioning processes, the changes appear procedural rather than security-focused. No specific security vulnerabilities or enhancements are mentioned.
Diff
diff --git a/managedservices/latest/userguide/personalize.md b/managedservices/latest/userguide/personalize.md index da692f7e0..7a71aa7a2 100644 --- a//managedservices/latest/userguide/personalize.md +++ b//managedservices/latest/userguide/personalize.md @@ -21 +21 @@ To learn more, see [Amazon Personalize](https://aws.amazon.com/personalize/). -Request access by submitting a Management | AWS service | Self-provisioned service | Add (review required) (ct-3qe6io8t6jtny) change type, and you need to specify which S3 bucket contains the data to be used by AWS personalize to generate the recommendations. This RFC provisions the following IAM roles to your account: `customer_personalize_console_role` and `customer_personalize_service_role`. +Request access by submitting a Management | AWS service | Self-provisioned service | Add (managed automation) (ct-3qe6io8t6jtny) change type, and you need to specify which S3 bucket contains the data to be used by AWS personalize to generate the recommendations. This RFC provisions the following IAM roles to your account: `customer_personalize_console_role` and `customer_personalize_service_role`. @@ -40 +40 @@ Amazon Personalize configuration is limited to resources without 'ams-' or 'mc-' -Amazon Personalize does not support the default KMS S3 key. If required to use KMS, create a custom key and add the following policy to it by opening an RFC with change type KMS Key | Create (Review Required): +Amazon Personalize does not support the default KMS S3 key. If required to use KMS, create a custom key and add the following policy to it by opening an RFC with change type KMS Key | Create (Managed automation):