I use CodePipeline with CodeCommit, CodeBuild, and CodeDeploy. My main use case is around building a small product. We've created a framework by leveraging AWS and Azure services. It functions as a table-driven approach, it allows us to switch features of the product on or off. We've set up CI/CD pipelines to enable these services, ensuring security and automatically propagating framework tables and metadata into the target environment. For example, as part of a customer's day zero setup, we provide them with the necessary tools to start their development. We utilize AWS CodeCommit to store our product components and then enable the CI/CD pipeline to seamlessly transfer these components from our tenancy to the customers.
In AWS CodePipeline ( /products/aws-codepipeline-reviews ), I have set up two different environments: development and production. The development environment is configured to be accessible only via VPN, while the production environment employs an advanced blue-green deployment strategy. This allows testing in a separate environment before full deployment to all users.
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.
The primary use case is for CICD pipelines. It is used to connect CodeBuild and CodeDeploy in a streamlined solution. The AWS CodePipeline only works with the code build and code deploy.
Associate DevOps Engineer at a computer software company with 1-10 employees
Real User
Top 5
Jun 25, 2024
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.
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.
Associate DevOps Engineer at a computer software company with 1-10 employees
Real User
Jan 24, 2024
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.
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.
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.
Senior ict specialist at Information& eGov Authority
Real User
Jan 6, 2023
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.
Virtualization and Cloud Architect at a transportation company with 10,001+ employees
Real User
Aug 18, 2021
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.
AWS CodePipeline enhances CI/CD processes through seamless AWS integrations and third-party apps, offering flexibility with parallel pipelines and dynamic agent management. Its robust security framework utilizes IAM roles and KMS for secure operations.AWS CodePipeline streamlines code deployment and CI/CD practices by orchestrating interactions with AWS services like CodeBuild, CodeDeploy, and CodeCommit. This integration boosts deployment capabilities while ensuring security with tools such...
I use CodePipeline with CodeCommit, CodeBuild, and CodeDeploy. My main use case is around building a small product. We've created a framework by leveraging AWS and Azure services. It functions as a table-driven approach, it allows us to switch features of the product on or off. We've set up CI/CD pipelines to enable these services, ensuring security and automatically propagating framework tables and metadata into the target environment. For example, as part of a customer's day zero setup, we provide them with the necessary tools to start their development. We utilize AWS CodeCommit to store our product components and then enable the CI/CD pipeline to seamlessly transfer these components from our tenancy to the customers.
In AWS CodePipeline ( /products/aws-codepipeline-reviews ), I have set up two different environments: development and production. The development environment is configured to be accessible only via VPN, while the production environment employs an advanced blue-green deployment strategy. This allows testing in a separate environment before full deployment to all users.
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.
The primary use case is for CICD pipelines. It is used to connect CodeBuild and CodeDeploy in a streamlined solution. The AWS CodePipeline only works with the code build and code deploy.
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.
I use the solution in my company to create an end-to-end flow for the clients' pipelines and to host different applications in different languages.
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.
I use the solution for my deployments.
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.
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.
We use the product for serverless integration AWS Lambda.
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.
I am using AWS CodePipeline to deploy our products for production.
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.
CodePipeline assists with the writing of code. It posts reports to our CodeCommit that is connected to our AWS source.
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.