AWS managedservices documentation change
Summary
Changed CodeDeploy provisioning process to use managed automation rather than requiring review
Security assessment
This mirrors changes in other service documentation about automation adoption, with no security-specific context provided in the diff. Existing IAM role security practices remain unchanged.
Diff
diff --git a/managedservices/latest/userguide/code-deploy.md b/managedservices/latest/userguide/code-deploy.md index e3fb71bff..b617993a8 100644 --- a//managedservices/latest/userguide/code-deploy.md +++ b//managedservices/latest/userguide/code-deploy.md @@ -13 +13 @@ Use AMS Self-Service Provisioning (SSP) mode to access AWS CodeDeploy capabiliti -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.