AWS managedservices documentation change
Summary
Changed RFC submission process from '(review required)' to '(managed automation)' for provisioning CodePipeline services
Security assessment
Change modifies the workflow type but doesn't introduce security-specific content or address vulnerabilities. Focuses on automation rather than security controls.
Diff
diff --git a/managedservices/latest/userguide/code-pipeline.md b/managedservices/latest/userguide/code-pipeline.md index e320b05a6..1b943ab73 100644 --- a//managedservices/latest/userguide/code-pipeline.md +++ b//managedservices/latest/userguide/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.