AWS CodeDeploy Reviews

I primarily use CodeDeploy for deploying infrastructure on AWS, specifically for deployments and modifications when changes are made. It is used to manage and create infrastructure.

I appreciate the feature that allows me to stop at a particular stage, giving me control over when to deploy. I can choose to deploy immediately or postpone it. CodeDeploy is also valuable because it allows deployment across multiple accounts. Its integration with other AWS services makes the process seamless.

My primary use case is for deploying work that I have done on the server. I have created YAML files that are in the local code, which automatically run to perform deployment into AWS via GitHub. Setting it up took some time, but subsequent runs take minutes.

I appreciate the feature for automating the deployment of code to the server. I can write Lambda expressions to do the deployment. These features streamline processes.

I monitor our GitHub repository and integrate it with our database using Pipeline. By creating code builds and deployment scripts, I connect them to our EC2 instances for automatic execution upon code pushes. Our setup includes production and development branches, each serving different purposes. Additionally, I store generated artifacts in an EC2 bucket and manage a three-layer application with frontend, backend, and database components, ensuring seamless collaboration with developers' needs.

Before implementing AWS CodeDeploy, our deployment process was manual and time-consuming. Developers would write code, save it locally, zip it, and then manually upload and unzip it on the server. This process required a lot of effort and time. After introducing AWS CodeDeploy, we streamlined our deployment process significantly. Now, developers can push code directly to GitHub, and CodeDeploy automates the deployment process to our AWS EC2 instances. This has not only saved time and effort but also optimized cost as AWS's pay-as-you-go model is more efficient compared to our previous hosting setup.

Basically, my company is for learning about code, but we don't use all the services that are available in the market. My company mostly relies on EC2, Lambda, RDS and S3 or sometimes we are using the load balancer,like ELB and CI/CD for AWS CodePipeline.

The feature I like the most in AWS CodeDeploy depends on my requirements, so if I want to copy some file inside the server or if I want to run something inside a server, AWS CodeDeploy is helpful. AWS CodeDeploy agent only runs everything on the server. Without an AWS CodeDeploy agent, we can't do anything inside the server through AWS CodePipeline.

The primary use case for AWS CodeDeploy is setting up continuous integration and continuous deployment pipelines or code pipelines.

AWS CodeDeploy integrates with other AWS services like Elastic Container Service, which provides a smooth deployment experience once everything is configured properly.

You can easily integrate AWS CodeDeploy with multiple services. For example, I can use the solution to access repositories and deploy images in the Kubernetes cluster. That will help me deploy my application seamlessly, providing high availability and resilience.

People face difficulties creating pipelines in AWS CodeDeploy. AWS should provide its own templates in the console so that I don't need to go anywhere else to get the template for AWS CodeDeploy or AWS CodeBuild.

The solution is used to run things on servers.

The product enables users to upload applications in S3 buckets. The product is easy to use. I haven’t had any issues with the product.