👀 Views: 34 💬 Answers: 1 📅 Created: 2025-06-02

aws codedeploy ec2 deployment bash

I just started working with I'm using AWS CodeDeploy to manage deployments for my application running on EC2 instances... I've configured a rolling update deployment strategy but I'm working with an scenario where the deployment fails with the behavior message `ApplicationStopFailed`. The deployment process is getting exploring at the 'Stop Application' phase, even though the instances appear healthy and running. I've checked the CodeDeploy logs and found the following behavior: `Failed to stop application on instance i-0123456789abcdef0`. Here's a snippet of my `appspec.yml` file: ```yaml version: 0.0 os: linux files: - source: / destination: /var/www/myapp hooks: AfterInstall: - location: scripts/install_dependencies.sh timeout: 300 runas: root ApplicationStop: - location: scripts/stop_server.sh timeout: 300 runas: root ApplicationStart: - location: scripts/start_server.sh timeout: 300 runas: root ``` In my `stop_server.sh` script, I'm ensuring that the application processes are terminating properly: ```bash echo "Stopping application..." pkill -f myapp ``` I tested the `stop_server.sh` script manually on the instance and it works as expected, stopping the application without issues. I've also ensured that the IAM role associated with the EC2 instance has sufficient permissions to execute the CodeDeploy actions. Additionally, I verified that my `CodeDeployAgent` is running the latest version (1.0.0-123) and there are no connectivity issues with the service. I'm puzzled as everything seems correct. What could be causing the `ApplicationStopFailed` behavior during the deployment? I'm using Bash LTS in this project. Any examples would be super helpful. I'm working on a desktop app that needs to handle this. How would you solve this?