AWS managedservices documentation change
Summary
Changed change type from 'review required' to 'managed automation' for service access requests and KMS key creation
Security assessment
The change modifies approval workflow but doesn't address specific vulnerabilities. KMS policy update maintains encryption requirements without new security context.
Diff
diff --git a/managedservices/latest/onboardingguide/personalize.md b/managedservices/latest/onboardingguide/personalize.md index ff05ccc01..c89b7a591 100644 --- a//managedservices/latest/onboardingguide/personalize.md +++ b//managedservices/latest/onboardingguide/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):