AWS CodePipeline Reviews

I use the solution in my company to automate code deployments, build pipelines, and deploy the application with source codes from GitHub webhooks.

I cannot specifically say which feature is helpful in the product. I can say that continuous integration helps pull source code more easily than manual pushing.

Based on my experience, I would say that AWS CodePipeline should be more like a tool that is not limited to AWS. It would be a much better tool if it could be made compatible with other cloud services as well since this is an area the product currently lacks.

The improvement I would like to see in AWS CodePipeline to support our company's CI/CD pipeline needs is possible if AWS resolves the multi-cloud compatibility issue in the tool currently.

I have been using AWS CodePipeline for a year. My company used to have a partnership with Amazon, but currently, we are a customer of the product.

I have not faced any issues with stability.

Scalability-wise, I rate the solution an eight out of ten.

Though my company had raised a ticket with the support team, it took three or four days for them to respond. I rate the technical support a six or seven out of ten.

For servers and microservices, I use Amazon ECS and EKS. For other services, I use AWS Lambda. I also use some tools for automation purposes of the pipelines and for other such related stuff.

The product's initial setup phase is easy compared to the general pipelines in the market.

The product can be deployed in two days, especially if I take into consideration areas like troubleshooting and the setup phase of the tool.

Compared to other cloud services, AWS CodePipeline falls a bit more on the pricey side. I see that the price of the product has been increasing for the past few years.

I use AWS CodePipeline for continuous integration and delivery in our company's projects since, with the product in place, multiple pipelines are built, and based on the requirements of different business branches, one can use the pipelines.

AWS CodePipeline improved our company's deployment process, especially in some parts of a project where our company had taken care of a deployment phase by using SonarQube to improve the static code testing that we had implemented on AWS CodePipeline, and it helped reduce the time in the area of code scanning, specifically static code scanning.

My company has not tried to integrate the product with the other services from Amazon or any other vendors.

I recommend the product to those who plan to use it. AWS CodePipeline's setup phase is easier compared to Jenkins. Compared to Jenkins, AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing.

I would recommend AWS CodePipeline over Jenkins. The setup phase of Jenkins is complex compared to AWS CodePipeline.

I rate the tool a seven out of ten.

We use the product for CI/CD implementation and integration with services like CodeDeploy, AmazonMQ, CloudWatch, and Fargate.

The most valuable feature of AWS CodePipeline lies in its role as a comprehensive umbrella service, including developer tools like CodeDeploy, CodeBuild, and CodeCommit. It helps develop CI/CD implementations with centralized management of code building, deployment, and version control.

The product’s pricing needs improvement.

We have been using AWS CodePipeline for two years.

The platform is 100% stability.

The platform is scalable.

The product doesn’t need to be set up. It offers a predefined configuration and adequate functionality to manage the implementation.

The product generates a return on investment particularly in terms of time optimization and efficient resource management.

AWS does not require upfront licenses or complex payment structures. It is a straightforward approach where you pay for the resources you consume as they offer a subscription-based licensing model.

The cost depends on various factors, including your usage patterns, requirements, and how it compares to other cloud service providers (CSPs). In comparison to some other CSPs, AWS services are more expensive.

Before selecting AWS CodePipeline, we conducted a thorough evaluation of various cloud service providers (CSPs) and their respective CI/CD services. AWS emerged as the preferred choice after considering factors such as usage patterns, management features, and overall performance.

With the help of AWS CodePipeline, we can easily utilize CodeDeploy and CodeBuild services for deployment purposes. It provides high integration between cloud services and critical applications running on-premises. It helps manage all the sources on a single pane of glass.

For monitoring and managing deployment, it offers integration with CloudWatch.

I recommend it to developers and rate it a nine out of ten.

When you do the microservices, you can build from the source code and package it to the docker image. After that, you can deploy the docker image to the container which is also situated in the AWS CodePipeline. 

The product is a one-stop solution that you can use to integrate, deploy and host your application. 

AWS CodePipeline doesn't offer much room for customization. 

I have been using this solution for three years. 

I would rate the product's stability a ten out of ten. 

I would rate AWS CodePipeline's scalability a ten out of ten. We use the solution every day, 24/7 to its maximum potential. 

AWS CodePipeline's technical support is good but it comes with a price. It will take you seven percent to ten percent of your total monthly cloud consumption.

Positive

We used Jenkins, GitHub, and GitLab. We switched to AWS CodePipeline since we have an AWS environment and it is more convenient. 

I would rate the product's setup a seven out of ten. There is a lot of work to be done if you need to integrate it with other tools. The solution's setup takes only a couple of hours to complete. We automated the tool's deployment and maintenance. 

The product is cost-effective. 

I would rate the product's pricing a five out of ten. 

I would rate the product an eight out of ten. If you have a multi-cloud infrastructure, then you need to consider Jenkins, GitLab or GitHub. 

I use the solution in my company, and we implement it whenever the tool is required in a project.

The need for the tool depends on the requirement. Some customers require closed and compact CI/CD pipelines; in such cases, we prefer AWS CodePipeline as the best option since it will be in a suitable environment. If the customers want some free sources, we can go with free sources. In our company, we have multiple CI/CD tools as well, but that completely depends on how much security the customers require and how much of a closed environment is required. AWS CodePipeline has some of the best features provided. The tool provides ample options, so we can use AWS Secrets Manager on those things where we can use AWS STS for some of the things, which will be much more helpful when working with a closed and secured environment.

Actually, the tool has multiple valuable features. When it comes to security, we have ample options to secure credentials, or whatever crucial data is there that is not supposed to be exposed. We can keep things in multiple environments, so we can create some environment variables from AWS Secrets Manager. From the environment variables, we can create different environments. The aforementioned area consists of one of the best features of the tool. Regarding additional features, we can use cross-account deployment, one of the tool's best features. When it comes to cross-account deployment, keeping one centralized account and deploying multiple applications in a different account is trending nowadays.

I have not thought about what needs improvement in the tool, but as of now, I am good with the tool. I am satisfied with the tool's performance, and I never came across any feature that it doesn't have. Whenever the customer requires something from the tool, all the features are present in AWS CodePipeline. If there is any option available in AWS CodePipeline that can offer integration with different products like SonarQube instead of just having to provide some URLs to our customers, then that would be great. It will make it easy for the integration of code analysis, and things can be done easily. I want to see more integration options. The industry doesn't go for paid versions, like CodeGuru, and some of the industries expect us to implement or integrate their tools with free products like SonarQube, which is supposed to provide a very free and basic structure. One would rather go for SonarQube rather than CodeGuru or other such tools. It would be best if AWS CodePipeline provided multiple integration options directly by providing some URLs.

I have been using AWS CodePipeline for two years. My company has a partnership with Amazon.

I have not seen any bugs in the tool. Its performance is quite good, which is similar to how any other CI/CD tool is supposed to perform.

Many people in my company use the product, but since it is a service-based company, everything completely depends on the choices and selections made. We are just here as a mentor to give suggestions and explain the advantages of what you get if you use AWS CodePipeline, Jenkins, and other such tools to our customers. In our company, we just give guidance on the importance of each tool to our customers, but selecting a CI/CD tool depends on the customers based on their budgets and their use cases. But we prefer CI/CD because it's a compact environment where there are fewer vulnerabilities. There is not much hard coding, and there is much more security, which is a more secure manner for the CI/CD pipeline.

Around 80 percent of my company's customers prefer AWS CodePipeline.

Scalability or other such factors don't have an impact on the product. AWS CodePipeline is a CI/CD tool that takes care of continuous integration and deployment. Where you are supposed to deploy the things, like if you are deploying at the cluster level, for your applications, there may be a need for auto-scaling. For CI/CD, you generally don't require any auto-scaling.

I haven't spoken to the tool's support team about CI/CD and other such areas. Things. Our company has recognized the advantages of AWS. We normally have some discussions with AWS' support team, but it is all associated with issues at the production level whenever it goes beyond our limits. We have a word with AWS' support team. For CI/CD, we don't contact AWS, but we are capable of managing it.

In our company, we normally don't use the installation process directly. It is one of the services we can directly build. As we are not performing in an on-premises model and are mostly at the cloud level, there are not many requirements. It is just a matter of a few clicks that will be needed to set up and keep the tool ready. If you come to CloudFormation in Terraform, things are not very difficult, and we can easily do it.

I haven't come across any challenges when setting up the product.

The price of the product depends on how many times you run it. The tool offers a pay-as-you-go model. The CI/CD pipeline can be considered as something that gets triggered per day at least four to five times, but sometimes, for the triggering part, there will be a certain amount that will be there. If the triggering is for a purpose, the user will incur a cost, but setting up the things won't cost anything.

Whether I would recommend the product to others or not is something that depends on whether you have multiple deployments and multiple cross-account integrations and if many other things are there for the application. If you are using just standard deployment using VCS, then I would suggest that you go with AWS CodePipeline. If you just want a simple single application deployment, then I prefer that you go for Jenkins, which is free of cost or open source. If one is keeping a centralized account for deploying multiple accounts of your application, I suggest you use AWS CodePipeline.

It is very easy to learn to use the product, and it is not a big deal since you need to just set up the things, and writing in buildspec YAML is not a big deal. Anyone can do it, even if you have an additional feature, such as restricting access to AWS CodePipeline by providing YALM. AWS CodePipeline is easier than Jenkins. Writing in pipeline scripts is something that people feel can be very difficult, but with buildspec YAML, it's quite easy to build it and add some logic, making it a process that is much easier compared to all CI/CD tools.

Different applications can be enhanced with AWS CodePipeline.

I rate the tool a nine out of ten.

I use the solution for making pipelines. I use it for deployments and CI/CD to make applications as required. I push code on CodeCommit. With the help of CodeCommit, I trigger the code to build and implement. Then, it will be deployed in Kubernetes using ECR and EKS.

Code deployment is the best feature. All the features in CodeCommit, CodePipeline, and CodeDeploy are important for automating the deployment process.

The support team’s response time must be improved.

I have been using the solution for one and a half years.

I rate the tool’s stability eight to nine out of ten. If I put everything correctly, it works.

I rate the tool’s scalability a seven out of ten. The product can be improved by implementing features available in other tools like Jenkins.

The support persons are experts in what they do. However, I must wait longer than expected to solve my issues.

Neutral

The initial setup felt difficult at first. However, as I learn how things work, it looks like something I can work on. The time taken for deployment depends on each project.

The product is quite expensive compared to other solutions.

Jenkins is much easier than CodePipeline. It is quite complex to build pipelines on CodePipeline compared to Jenkins.

Sometimes, I use CodePipeline to integrate applications on my EC2 server. Sometimes, I use it with AWS Lambda. I am working as a DevOps engineer. I provide technical support to customers who are using the product. I have to demonstrate the customers' issues and try to resolve them. I recommend the solution to experienced people. If someone uses Amazon’s DevOps tool, I will recommend the solution. Otherwise, I will not recommend the product. Overall, I rate the product a seven to eight out of ten.

We use the solution to deploy different applications and connect third-party APIs to various projects. I commonly use the Jenkins CI/CD pipeline. I've used it to set up servers. The architecture is very complex and needs a lot of connections, storage, security, and network. We need CodePipeline to complete these processes faster.

I love the fact that the tool can be integrated with different applications. For example, we can integrate pipelines with Slack to schedule tasks and run a bot. If we want to get notified about changes in our server, we can link the pipeline with Slack. It creates a channel where we receive updates on what's happening on the server. It notifies us if the IP address has changed or if there is something wrong with the server. The integration with other applications is fabulous.

The setup time is a bit long. We need a lot of experience to work with it. We need a lot of troubleshooting experience. We need to contact support if things get out of hand.

I have been using the solution for a year and a half.

The tool is very stable. I have not had any issues with the applications I have deployed. I only faced issues during deployment.

The tool is very, very scalable. I rate the scalability a nine out of ten. We need only one engineer to do the updates.

The support team is good. The response is good. I've not had very complex problems, but for the problems I faced, I received good support.

Positive

The initial setup is straightforward, but it is a bit difficult. The deployment takes five to ten minutes. It has a good latency.

People using the solution for the first time must have good experience in troubleshooting. If we do something wrong, we should be patient enough to solve it. We should not get frustrated. A good networking experience in AWS and a good knowledge of IP addresses will also be helpful. Overall, I rate the product a nine out of ten.

Our primary use case for CodePipeline is speeding up our development process. The solution is highly automated and allows us to build and deploy code without any effort. It's automatically initiated once I commit my code. 

CodePipeline also helps me to find bugs quickly, increasing my release speed. On the other hand, it helps our customers receive our releases regularly and incrementally. CodePipeline helps us out with our delivery and our customers are happy to see our results in real time through it.

The solution is a continuous integration and delivery mechanism that helps us a lot in delivering our software. This is the most powerful benefit we get from using CodePipeline. It's one of those DevOps concepts recommended for use within the software development lifecycle.

I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly. We can also transition between the environments with CPLEX. I think CodePipeline is brilliant. 

CodePipeline allows you to focus on your program or your software, rather than worrying about deployment and the build stuff. We save quite a bit of time with CodePipeline.

The only area in my opinion that needs to be improved is the time between build and deployment. AWS should improve build time. We wait up to seven minutes for deployment.

In the next release, I would like to see fewer timeout errors.

I have been using AWS CodePipeline for around three years now.

I have had timeout errors in CodePipeline before. However, this has been acceptable for me as it was in development time and not in production.

My opinion is that this solution is scalable. It's good and it accepts a wide range of programming languages. I can manipulate the order and manage it regardless of the technology I'm using. It's very scalable. It's brilliant; a solution I like very much. It saves a lot of build and deployment effort if we compare it to old-style development. We consume a lot of time building and deploying, just to see our products running.

I have not contacted their tech support.

My impression is that this product is easy to set up. Everything including the documentation is provided.

I would recommend this solution to others as it is one of the most valuable products that can help any DevOps environment for software.

Overall, I would rate this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

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 AWS CodePipeline for agent deployments, Kubernetes orchestrations, and Argo deployments. We integrate it with multiple applications in the DevOps pipeline for software compression analysis purposes.

The product is cost-effective and integrates well with the AWS environment. It helps reduce complexities in scenarios involving Jenkins and other CI/CD tools. The integration provides an additional security layer.

There could be a possibility of deploying tag-based conditions for different environments using the same code base similar to GitHub. Implementing tag-based conditions in the build spec file is possible, but the process can be simpler. They could provide this tagging functionality in the UI itself. The users could decide pipeline triggers based on the predefined rules.

We have been using AWS CodePipeline for two and a half years.

The platform is stable. It works 99.99% of the time as per the service level agreement.

Around 90% of our executives are using CodePipeline. Only ten percent of executives are using GitLab.

AWS provides user-friendly support services. They resolve the issues instantly.

Positive

CodePipeline is a managed service by AWS. The initial setup process is user-friendly and straightforward.

The product is inexpensive compared to Jenkins and GitLab, where we incur extra costs for maintaining separate servers. AWS offers free business or enterprise support services.

We have integrated AWS CodePipeline with AWS services such as Amazon EKS, ECS, and EC2 for virtual machine deployments. We can integrate it with Lambda for event triggering. It is a useful service. It is straightforward to understand for new users who are learning the application deployment through pipelines. While Jenkins requires installation, server setup, and security considerations, CodePipeline simplifies the process by handling the underlying infrastructure, allowing users to concentrate solely on pipeline scripts.

I rate the product an eight out of ten.

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.