AWS CodePipeline Reviews

I am using AWS CodePipeline to deploy our products for production.

The most valuable feature of AWS CodePipeline is the flexibility of the configuration.

The solution could improve the documentation. Sometimes we have some issues with the documentation not updating after releasing .NET 6. We had some issues with building the code pipeline, and it was not updating the documentation. It's better to update the code documentation.

In a future release, they should improve the UX and add some additional features.

I have been using AWS CodePipeline for approximately three years.

AWS CodePipeline is stable once it is configured correctly.

We have four developers using this solution in my company.

The solution is scalable, we have multiple pipelines.

I have not contacted the support from AWS CodePipeline.

The initial setup of AWS CodePipeline is challenging because of the lack of updates to the documentation. The full implementation takes approximately two weeks.

We were using other Amazon solutions and this is why we chose AWS CodePipeline.

My advice to others is the implmentation process will take some time because of the poor documentation.

I rate AWS CodePipeline a six out of ten.

We use CodePipeline for deploying some of the applications that we have for AWS.

Ours is a multi-cloud hybrid cloud approach. We have Azure, AWS, Google Cloud, and then we use CI/CD pipelines - our core pipeline tools - from each cloud. For example, on Azure, we use Azure DevOps that integrates with our GitHub on-prem. That's what we use for deploying anything on Azure. The same GitHub. It is also used on Google Cloud. We don't use the native tools from any of the clouds. For example, the CodePipeline from AWS or Deployment Manager from Google Cloud. We try to avoid those. We are moving towards Terraform with a GitHub integration as of our source code repository or pipeline, CI/CD pipeline. No matter what the cloud, we use our on-prem resources. We try to avoid using the cloud.

The solution is pretty stable. 

It's a perfect solution if you are just using AWS.

The pricing is okay.

Since we are very price-conscious, we would like the solution to be cheaper. If it was, we would use it more. 

CodePipeline is not an option for us at all, as CodePipeline is strictly tied to AWS and we have workloads on Azure and Google. We don't want our workloads to be running from source code that is running in AWS. That's why we prefer on-prem for source code with Terraform and GitHub and then use that to deploy across the cloud. That's our approach.

The last time we used the solution was for a project about a year ago.

The solution is pretty stable. Obviously, there are bugs dealing with it, however, it is a pretty good tool. It doesn't give us too many issues. 

Whenever we get a requirement for an application deployment in the public cloud, we usually compare if that service is available in all of the three clouds and then we run those pricing estimates to see which is cheaper on which cloud. I work as an enterprise company and we have multiple tabs from all three. Whoever gives us the cheaper credit, that's what we go with - which is cheaper.

I'd give it a ten out of ten. It's the best tool. It's good for AWS, however, if you're talking about multi-cloud, you can't use it.

CodePipeline assists with the writing of code. It posts reports to our CodeCommit that is connected to our AWS source. 

In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps. Using AWS Pipeline, we are able to add our requirements and it will be automatically scaled. This saves us time and connects to services like EKS. 

 AWS CodePipeline does a very good job as compared to Jenkins. We have saved money using this solution as we we pay for data as it is needed. AWS also offers great security.

I have been using this solution for one year. 

This is a very stable solution.

This is a scalable solution. There is also an option to autoscale. 

The customer service and support for this solution is good. 

Neutral

There are two key roles needed for the setup including the service role for AWS and the service role for CodePipeline. If there are many dependancies involved in the setup, it may take a long time. If a Docker file is already executed, the setup will be quicker. 

The pricing of this solution is dependent upon your needs including how many jobs you daily and how many times the developer will be changing codes and completing deployments.

I would rate this solution a nine out of ten.