AWS managedservices documentation change
Summary
Changed RFC change type from 'Add (review required)' to 'Add (managed automation)' for provisioning Code services
Security assessment
Change modifies provisioning workflow but doesn't address security vulnerabilities or add security documentation. The update appears to be about process automation rather than security controls.
Diff
diff --git a/managedservices/latest/onboardingguide/code-pipeline.md b/managedservices/latest/onboardingguide/code-pipeline.md index ec2593518..4f1dd26e1 100644 --- a//managedservices/latest/onboardingguide/code-pipeline.md +++ b//managedservices/latest/onboardingguide/code-pipeline.md @@ -13 +13 @@ Use AMS Self-Service Provisioning (SSP) mode to access AWS CodePipeline capabili -To onboard CodeCommit, CodeBuild, CodeDeploy, and CodePipeline with a single RFC, submit the Management | AWS service | Self-provisioned service | Add (review required) (ct-3qe6io8t6jtny) change type and request the three services: CodeBuild, CodeDeploy and CodePipeline. Then, all three roles, `customer_codebuild_service_role`, `customer_codedeploy_service_role`, and `aws_code_pipeline_service_role` are provisioned in your account. After provisioning in your account, you must onboard the role in your federation solution. +To onboard CodeCommit, CodeBuild, CodeDeploy, and CodePipeline with a single RFC, submit the Management | AWS service | Self-provisioned service | Add (managed automation) (ct-3qe6io8t6jtny) change type and request the three services: CodeBuild, CodeDeploy and CodePipeline. Then, all three roles, `customer_codebuild_service_role`, `customer_codedeploy_service_role`, and `aws_code_pipeline_service_role` are provisioned in your account. After provisioning in your account, you must onboard the role in your federation solution.