I remember it was a Node.js API that I deployed to some EC2 instances. I was trying to use PM2, a process manager, to deploy the application to the end users.
Digital Technology Analyst at a tech services company with 10,001+ employees
MSP
Top 10
2025-02-12T09:18:00Z
Feb 12, 2025
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.
Systems Lead Developer at Columbia University Medical Center
Real User
Top 20
2025-01-20T13:43:14Z
Jan 20, 2025
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.
We use CodeDeploy to deploy services onto different platforms within AWS, such as EC2 services or containers like EKS, which is part of Kubernetes, or Elastic Container Services like ECS. This depends on the platform we wish to deploy on.
I mostly use it for Jenkins. While using Jenkins, I have been using AWS CodeDeploy. We have been doing deployments using EKS and containerized cluster deployments. Mostly on-prem applications only. We have been working on it.
I recommended using AWS CodeDeploy for a small customer, an institute that wanted their application replicated on AWS. AWS CodeDeploy was chosen for its simplicity and ease of integration. Unlike other tools that require extensive scripting for each stage, it offers a drag-and-drop functionality, making the deployment process easy.
Release Automation streamlines the deployment process of applications, offering efficiency and reducing manual errors. It facilitates faster release cycles and ensures consistency across environments.Automating the release process enhances operational productivity by orchestrating and standardizing it. It integrates with existing tools to provide a cohesive workflow from development to deployment. Its flexibility adapts to different requirements, ensuring each release is smooth and...
I remember it was a Node.js API that I deployed to some EC2 instances. I was trying to use PM2, a process manager, to deploy the application to the end users.
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.
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.
We use CodeDeploy to deploy services onto different platforms within AWS, such as EC2 services or containers like EKS, which is part of Kubernetes, or Elastic Container Services like ECS. This depends on the platform we wish to deploy on.
I mostly use it for Jenkins. While using Jenkins, I have been using AWS CodeDeploy. We have been doing deployments using EKS and containerized cluster deployments. Mostly on-prem applications only. We have been working on it.
The solution is used to run things on servers.
I recommended using AWS CodeDeploy for a small customer, an institute that wanted their application replicated on AWS. AWS CodeDeploy was chosen for its simplicity and ease of integration. Unlike other tools that require extensive scripting for each stage, it offers a drag-and-drop functionality, making the deployment process easy.
We use CodeDeploy to deploy code across multiple instances and servers.