AWS CodePipeline Reviews

I use the solution for CI/CD. We use it for continuous integration and delivery of our projects. It's primarily used to deploy applications to both development and live servers.

The tool's recent version helps us to run pipelines in parallel. The integration with other AWS services has greatly impacted our use of AWS CodePipeline. It made tasks such as integrating with Jira and provisioning instances much easier.

The tool's UI is wonderful. 

AWS CodePipeline functions well, but there's room for improvement in providing technical support to regular customers who haven't purchased developer support. I mean, having it available for everyone, even if it's not a 24-hour service. It would be more useful if specific support hours were available for assistance.

I have been using the product for nine months. 

I rate the tool's stability a ten out of ten. 

I rate the solution's scalability a ten out of ten. 

I have used GCP before. 

The tool's deployment is manageable. 

AWS CodePipeline is quite affordable. I've been running around four pipelines and the cost is around one dollar per month. It rarely exceeds two dollars.

I rate the tool a ten 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.

We use the product for serverless integration AWS Lambda.

The product helps with testing the code. We can integrate it to build and deploy code. We can create an automation template as well.

AWS CodePipeline has valuable integration features.

The product could be integrated easily with other platforms, such as GitHub. The migration process from one source code to another needs improvement. It should support different codes and tools.

We have been using AWS CodePipeline for two years. At present, we use the latest version.

It is a stable platform. I rate its stability a ten out of ten.

I rate the product’s scalability a six out of ten.

The technical support team’s response time depends on the criticality of the issue.

We have used GitHub before. We switched to AWS CodePipeline for better security features while integrating with other platforms.

The configuration is difficult in the beginning. It becomes easier to deploy with the help of Terraform.

I rate AWS CodePipeline an eight out of ten.

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.

I have used AWS CodePipeline as part of my work deploying applications, particularly an e-commerce app for a customer on AWS. I designed the process starting with building Docker images on a local machine and then pushing them to AWS ECR (Elastic Container Registry). 

After that, I configured the necessary infrastructure using Terraform and used AWS CodePipeline along with other services like CodeDeploy and CodeCommit to manage the deployment process.

AWS CodePipeline has improved our deployment efficiency, allowing us to orchestrate services such as CodeBuild, CodeDeploy, and CodeCommit seamlessly within AWS. Its native integration with AWS makes it easier to manage processes and improve deployment workflows within our organization.

AWS CodePipeline's most valuable feature is its seamless integration with other AWS services, making it easier to orchestrate deployment processes. It scales easily, and since it's native to AWS, most functionalities are integrated naturally, providing a consistent environment. The fact that alternatives like Jenkins and GitHub Actions require more effort to integrate makes CodePipeline the preferred choice.

AWS CodePipeline works effectively, and I haven't identified any specific areas needing improvement as it has been quite satisfying in terms of deployment needs. Feedback from clients has also been positive, indicating satisfaction with the service.

I have been using AWS CodePipeline for over two years now.

I have not encountered any stability issues with AWS CodePipeline since I began using it. It has been quite efficient and reliable for all my deployment tasks.

AWS CodePipeline scales easily and effectively, supporting various deployment models and workloads. It offers significant flexibility whether deploying on EC2 instances or using container services.

AWS support is excellent. Whenever I encounter issues, the support team is always available and helpful.

Positive

In the past, I have used solutions like Jenkins and GitHub Actions. However, AWS CodePipeline is more integrated within AWS, making it the preferred choice for projects hosted on AWS.

AWS CodePipeline and its associated services do not incur significant additional charges. The cost primarily comes from deploying other AWS resources like EC2 and S3 alongside the pipeline.

I have considered Jenkins and GitHub Actions as alternatives. However, the native integration of AWS CodePipeline within AWS makes it much easier to use in that environment.

I recommend AWS CodePipeline, but it depends on the type of project and needs of the customer. Based on my experiences, a rating of seven or eight out of ten reflects its capabilities. It's essential to consider the use case when recommending solutions.