<p>A bit too long for a comment, so converting to an answer:</p>
<p>That's super broad and highly depends on your final needs IMHO, if you're full AWS and ok with being vendor locked down, then code commit/code build/code pipeline is great as it's nicely integrated now.</p>
<p>If you have needs outside pure AWS services, that may get harder, for exemple if you plan on stretching on multiple cloud vendors in a always on DRP (Disaster Recovery Plan), that's probably not the better tool.</p>
<p>My take is that for a full AWS things, AWS products are good and <em>usually</em> soften the edges, but if you need to interact with things out of AWS, there's solution more aimed at CI/CD like Bitbucket, as you said but that'd be my last choice, CircleCi, Travis, Github Actions and Gitlab.</p>
<p>The CI/CD cost is rarely a concern, even if you have a super large company with dozens of products, the code repository and user management costs will probably out-stand the pipeline costs by a large factor unless you run thousands of pipelines per day.</p>
<p>My <em>personal</em> preference goes to Gitlab for its versatility in pipelines, how easy internal runners are to setup and to avoid vendor lock down on the hosting.</p>

CC BY-SA 4.0
2021-03-30T19:31:41.670Z
2021-03-30T19:31:41.670Z
Tensibai
<p>What are the advantages of using AWS Codepipeline/code build for our pipeline over the bitbucket pipeline. ?</p>
<p>Some of the factors that I can think of:</p>
<ol>
<li>Pricing?</li>
<li>Pipeline for a serverless application</li>
<li>integration with AWS</li>
<li>services</li>
<li>Speed of execution</li>
</ol>

<amazon-web-services><continuous-integration><continuous-deployment><bitbucket-pipelines><aws-codepipeline>
Advantages of using Code-pipeline and Codebuild for CI/CD over Bitbucket pipeline?
systemdebt
# Advantages of using Code-pipeline and Codebuild for CI/CD over Bitbucket pipeline?

(Asked by: username_0 on 2021-03-30)

What are the advantages of using AWS Codepipeline/code build for our pipeline over the bitbucket pipeline. ?

Some of the factors that I can think of:

1. Pricing?
2. Pipeline for a serverless application
3. integration with AWS
4. services
5. Speed of execution

**Tags:** amazon-web-services, continuous-integration, continuous-deployment, bitbucket-pipelines, aws-codepipeline


---

## 1 answers

### Answer by username_1 on 2021-03-30. Score: 1 | Accepted answer

A bit too long for a comment, so converting to an answer:

That's super broad and highly depends on your final needs IMHO, if you're full AWS and ok with being vendor locked down, then code commit/code build/code pipeline is great as it's nicely integrated now.

If you have needs outside pure AWS services, that may get harder, for exemple if you plan on stretching on multiple cloud vendors in a always on DRP (Disaster Recovery Plan), that's probably not the better tool.

My take is that for a full AWS things, AWS products are good and *usually* soften the edges, but if you need to interact with things out of AWS, there's solution more aimed at CI/CD like Bitbucket, as you said but that'd be my last choice, CircleCi, Travis, Github Actions and Gitlab.

The CI/CD cost is rarely a concern, even if you have a super large company with dozens of products, the code repository and user management costs will probably out-stand the pipeline costs by a large factor unless you run thousands of pipelines per day.

My *personal* preference goes to Gitlab for its versatility in pipelines, how easy internal runners are to setup and to avoid vendor lock down on the hosting.


---

