AWS managedservices documentation change
Summary
Updated CodeBuild/CodeDeploy/Pipeline onboarding to use 'managed automation' RFCs
Security assessment
The change automates service role provisioning but does not demonstrate remediation of security risks or introduction of new security features. The roles themselves remain unchanged.
Diff
diff --git a/managedservices/latest/onboardingguide/code-build.md b/managedservices/latest/onboardingguide/code-build.md index f16246845..78f8ee7f9 100644 --- a//managedservices/latest/onboardingguide/code-build.md +++ b//managedservices/latest/onboardingguide/code-build.md @@ -13 +13 @@ Use AMS Self-Service Provisioning (SSP) mode to access AWS CodeBuild capabilitie -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.