An application specification file (AppSpec file), which is unique to AWS CodeDeploy, is a YAML-formatted or JSON-formatted file. The AppSpec file is used to manage each deployment as a series of lifecycle event hooks, which are defined in the file. The AppSpec file is used to:
You can learn more about the AppSpec File Structure here.
You will now deploy your application to the EC2 instances launched by the Auto Scaling group.
Take a moment to browse and view the CodeDeploy structure for your application, located in the codedeploy directory.
You’ll need to modify the CodeDeploy deployment scripts in order to use the RDS database instance you previously created. Run the following command to edit codedeploy/scripts/configure_db.sh with the Endpoint of your database instance (e.g. runningamazonec2workloadsatscale.ckhifpaueqm7.us-east-1.rds.amazonaws.com) .
# Grab the RDS endpoint
rds_endpoint=$(aws rds describe-db-instances --db-instance-identifier runningamazonec2workloadsatscale --query DBInstances[].Endpoint.Address --output text)
sed -i.bak -e "s/%endpoint%/$rds_endpoint/g" codedeploy/scripts/configure_db.sh
Take a look at the file on the Cloud9 editor to confirm the script code has been updated with your Database endpoint.
Then clone the Koel GitHub repo:
cd ~/environment/ec2-spot-workshops/workshops/running-amazon-ec2-workloads-at-scale/
git clone https://github.com/phanan/koel.git
cd koel && git checkout v3.7.2
You’ll get an update about being in ‘detached HEAD’ state. This is normal.
Apply fix to composer.json:
sed -i.bak -e "s/vfsStream/vfsstream/g" composer.json
Next, copy the CodeDeploy configs into the root level of the koel application directory:
cp -avr ../codedeploy/* .
After reviewing and getting comfortable with the CodeDeploy configs, go ahead and create the CodeDeploy application:
aws deploy create-application --application-name koelApp
Browse to the AWS CodeDeploy console, make sure your region is selected in the upper right-hand corner dropdown, and then click on your application to check out your newly created application.
The CodeDeploy console will not default to your current region. Please make sure to click on Select a Region in the upper right-hand corner and select your region in the dropdown.
Next, push the application to the CodeDeploy S3 bucket that the initial CloudFormation template created (which you loaded to the $codeDeployBucket environment variable at the beginning of the workshop):
aws deploy push --application-name koelApp --s3-location s3://$codeDeployBucket/koelApp.zip --no-ignore-hidden-files
You will get output similar to the following. This is normal and correct: To deploy with this revision, run: aws deploy create-deployment –application-name koelApp –s3-location bucket=runningamazonec2workloadsatscale-codedeploybucket-11wv3ggxcni40,key=koelApp.zibundleType=zip,eTag=870b90e201bdca3a06d1b2c6cfcaab11-2 –deployment-group-name –deployment-config-name –description
Check the content of the S3 bucket, browsing the S3 console and clicking on the bucket (you can find the bucket name on the value of codeDeployBucket in the CloudFormation stack outputs or running $ echo $codeDeployBucket in your terminal). This is the bucket you’re using for your code deployments. You should see your application deployment bundle inside the bucket.
Run the following command to edit deployment-group.json with the value of %codeDeployServiceRole% from the CloudFormation stack outputs, and then create the deployment group:
cd ..
sed -i.bak -e "s#%codeDeployServiceRole%#$codeDeployServiceRole#g" deployment-group.json
aws deploy create-deployment-group --cli-input-json file://deployment-group.json
Browse to the AWS CodeDeploy console, make sure your region is selected in the upper right-hand corner dropdown, click on your application, and then click on the Deployment groups tab to check out your newly created deployment group.
The CodeDeploy console will not default to your current region. Please make sure to click on Select a Region in the upper right-hand corner and select your region in the dropdown.
Finally, edit the application by editing deployment.json and replacing the value of %codeDeployBucket% from the CloudFormation stack outputs.
sed -i.bak -e "s/%codeDeployBucket%/$codeDeployBucket/g" deployment.json
Take look at the configuration file and then create a deployment running:
aws deploy create-deployment --cli-input-json file://deployment.json
Note the deploymentId.
Browse to the AWS CodeDeploy console, make sure your region is selected in the upper right-hand corner dropdown, and then click on your Deployment ID to monitor your application deployment. At the bottom under Deployment lifecycle events, you will see a list of the EC2 instances belonging to your auto scaling group. To monitor the individual deployments to each of the instances, click on View Events.
The CodeDeploy console will not default to your current region. Please make sure to click on Select a Region in the upper right-hand corner and select your region in the dropdown.
As the application is successfully deployed to the instances, they will pass their target group health checks and be marked as healthy in the target group status. Browse to the Target Group console, select your target group, and click on the Targets tab.
Once one or more instances are marked with a status of healthy, browse to the Load Balancer console, select your load balancer, and copy the DNS name (URL) of your load balancer (e.g. http://runningAmazonEC2WorkloadsAtScale-115077449.us-east-1.elb.amazonaws.com).
Open your web browser and browse to the DNS name (URL). You will see the login page to your application. Login in with the default email address ‘admin@example.com’ and default password ‘admin-pass’.
The EFS file system is mounted on every instance at /var/www/media in order to create a shared location for your audio files. Mount the EFS file system in the Cloud9 environment and copy some mp3s to the file system. The EFS file system id created by CloudFormation is loaded on the $fileSystem environment variable.
mkdir -p ~/environment/media
sudo mount -t efs $fileSystem:/ ~/environment/media
sudo chown ec2-user. ~/environment/media
sudo cp -av *.mp3 ~/environment/media
Back in Koel, under MANAGE, click on Settings. Click on Scan. Play around and enjoy some audio on your music service.
[Optional] If you’d like, find a few more mp3s on the web and upload them to the directory ~/environment/media in the Cloud9 environment. After uploading them, be sure to re-scan the media directory.