Code Pipeline

0

So we have at least 60 projects and if we wanted to do CI/CD would we create service roles for EACH one of those projects or just one service role for the CI/CD to use to create and make stuff?

Every example seems to have a single project and not a use case for a larger company.

已提問 5 年前檢視次數 276 次
4 個答案
0

Hello!

If all the pipelines are in the same account, then you can re-use the same pipeline role for all of them, no problem!

Matthew

Edit: You can also re-use the artifact bucket as well :)

Edited by: mattsainsaws on Feb 19, 2019 2:44 PM

已回答 5 年前
0

The security folks would like us NOT to reuse roles and have separation of security for each project. Just wonder is that really what dev shops are doing?

已回答 5 年前
0

Well, you can create separate roles for each pipeline too, if you prefer. I would recommend using CloudFormation if you have that number of pipelines because it would be quite arduous to create them all manually.

Personally I would create a new role per pipeline that has just enough permissions to do what it needs. Although pipelines tend to have quite broad permissions in general so it's important to make sure only the codepipeline principal can assume them.

I spoke to a colleague who speaks to a lot of CodePipeline customers, and he said that enterprise customers tend to have an automated process for creating pipelines (eg., CloudFormation or some custom tool) and that process creates a separate pipeline role (and sometimes even account) for that pipeline. Hopefully that gives you some ideas on how to create lots of pipelines in a secure way.

已回答 5 年前
0

Thank you so much !

已回答 5 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南