{"id":4716,"date":"2016-05-17T08:06:27","date_gmt":"2016-05-17T08:06:27","guid":{"rendered":"http:\/\/blog.cloudthat.com\/?p=4716"},"modified":"2024-06-25T11:12:39","modified_gmt":"2024-06-25T11:12:39","slug":"install-wordpress-using-aws-codepipeline","status":"publish","type":"blog","link":"https:\/\/www.cloudthat.com\/resources\/blog\/install-wordpress-using-aws-codepipeline","title":{"rendered":"Install WordPress using AWS Codepipeline"},"content":{"rendered":"

In this blog we are going to show how we can install a WordPress with AWS Codepipeline.<\/p>\n

Before we begin the demo, let us brief you about the services which will be used.<\/p>\n

Amazon Web Services (AWS) is providing three services namely CodeCommit, CodeDeploy, CodePipeline as Developer Tools for the developers, which lets them to focus more on their application rather than deployment.<\/p>\n

\"blog-cover-image\"<\/a><\/p>\n

CodeCommit <\/strong><\/h2>\n

CodeCommit\u00a0<\/strong>hosts private Git repositories, lets we\u00a0to store code securely. You can store anything, anytime and integrate with other AWS & third-party services. Files can be easily migrated from any Git-based repository to AWS CodeComit.<\/p>\n

CodeDeploy<\/strong><\/h2>\n

CodeDeploy is developers service, which allows the users to deploy application (contains content such as code, web, scripts, etc). It helps in automated deployments, reduces downtime, have centralized control and easy to adopt.<\/p>\n

CodePipeline<\/strong><\/h2>\n

CodePipeline is a continuous delivery service, which lets you to automate your release process using your favorite tools such as Amazon S3, CodeCommit, AWS Elastic Beanstalk, AWS CodeDeploy and Jenkins as well. You can view the progress at a glance. It helps in speeding up delivery while improving quality. It contains many stages to test your code before releasing.<\/p>\n

Let\u2019s begin with pre-requisites<\/p>\n

Working knowledge of Linux, Amazon EC2, SNS, IAM, RDS & Git.<\/p>\n

Region : N.Virginia<\/p>\n

Pre-requisites <\/strong><\/p>\n

We need to have two IAM roles: a Service Role and an Instance Profile Role.<\/p>\n

Create a role named as Service Role <\/strong>and paste the below policy.<\/p>\n

 <\/p>\n

{\r\n    \"Version\": \"2012-10-17\",\r\n    \"Statement\": [\r\n        {\r\n            \"Action\": [\r\n                \"autoscaling:PutLifecycleHook\",\r\n                \"autoscaling:DeleteLifecycleHook\",\r\n                \"autoscaling:RecordLifecycleActionHeartbeat\",\r\n                \"autoscaling:CompleteLifecycleAction\",\r\n                \"autoscaling:DescribeAutoscalingGroups\",\r\n                \"autoscaling:PutInstanceInStandby\",\r\n                \"autoscaling:PutInstanceInService\",\r\n                \"ec2:Describe*\",\r\n                \"sns:*\",\r\n                \"codecommit:*\",\r\n                \"codedeploy:*\",\r\n                \"codepipeline:*\",\r\n                \"codecommit:GetBranch\",\r\n                \"codecommit:GetCommit\",\r\n                \"codecommit:UploadArchive\",\r\n                \"codecommit:GetUploadArchiveStatus\",\r\n                \"codecommit:CancelUploadArchive\",\r\n                \"s3:*\"\r\n            ],\r\n            \"Effect\": \"Allow\",\r\n            \"Resource\": \"*\"\r\n        }\r\n    ]\r\n}\r\n<\/pre>\n
Once the IAM role is created, we need to establish a trusted relationship for this role with AWSCodeDeploy. Modify trust relationship policy for this particular role and set it to below mentioned policy :<\/p>\n
{ \r\n\"Version\": \"2012-10-17\", \r\n\"Statement\": [    \r\n    {      \r\n    \"Sid\": \"\",      \r\n    \"Effect\": \"Allow\",      \r\n    \"Principal\": {       \r\n    \"Service\": [            \r\n        \"codedeploy.us-east-1.amazonaws.com\",            \r\n        \"codedeploy.us-west-2.amazonaws.com\"        \r\n    ]      \r\n    },      \r\n    \"Action\": \"sts:AssumeRole\"    \r\n    }  \r\n] \r\n}\r\n<\/pre>\n
Instance Profile Role<\/strong>: EC2 instances needs to be launched with proper permissions to access files from S3 buckets.<\/p>\n
{  \r\n    \"Version\": \"2012-10-17\",  \r\n    \"Statement\": [    \r\n    {      \r\n        \"Action\": [        \r\n            \"s3:Get*\",        \r\n            \"s3:List*\"      \r\n        ],      \r\n        \"Effect\": \"Allow\",      \r\n        \"Resource\": \"*\"    \r\n    }  \r\n    ] \r\n} \r\n<\/pre>\n
Note:\u00a0<\/strong>Go to IAM (Identity Access Management), select the Role named AWS-Codepipeline-Service\u00a0<\/b>and paste the below conditions in the policy.<\/p>\n
{\r\n  \"Action\": [  \r\n      \"codecommit:GetBranch\",\r\n      \"codecommit:GetCommit\",\r\n      \"codecommit:UploadArchive\",\r\n      \"codecommit:GetUploadArchiveStatus\",      \r\n      \"codecommit:CancelUploadArchive\"\r\n            ],\r\n  \"Resource\": \"*\",\r\n  \"Effect\": \"Allow\"\r\n},<\/pre>\n
Step 1<\/span><\/b>: Launch an EC2 instance with the Instance Profile role. While launching the instance Under Configure Instance Details <\/b>page, expand Advanced Details, and in the User data field, type the following:<\/span><\/p>\n
sudo yum update \r\nsudo yum install aws-cli \r\ncd \/home\/ec2-user \r\naws s3 cp s3:\/\/aws-codedeploy-us-east-1\/latest\/install . --region us-east-1 \r\nchmod +x .\/install \r\nsudo .\/install auto\r\n<\/pre>\n
\"wp-1\"<\/a><\/p>\n
Step -2<\/strong> Go to AWS management console, select CodeCommit.<\/p>\n
Step -3<\/strong> Click Create new repository to create a repository<\/p>\n
\"wp-2\"<\/a><\/p>\n
Step \u2013 4 <\/strong>Create a repository by filling name and description.<\/p>\n
\"wp-3\"<\/a><\/p>\n
Step \u2013 6 <\/strong>Click Clone URL<\/strong>, then select SSH<\/strong> we will get url for cloning the repo in our local machine. Copy url,<\/strong> will be useful later in the process.<\/p>\n
\"wp-4\"<\/a><\/p>\n
 <\/p>\n
Step \u2013 7 <\/strong>In your local system (Linux), do AWS configure. <\/strong>Move to \/tmp\/ <\/em>and clone the codecommit repository.<\/p>\n
Step \u2013 8 <\/strong>Move to cloned repo, keep the zip file here containing your WordPress installation. Make changes in wp-config.php<\/strong> (like \u2018DB_HOST\u2019, \u2018localhost\u2019). After commiting push it into repo.<\/p>\n
For verification, go to CodeCommit console, there you can find the details.<\/p>\n
Step \u2013 9 <\/strong>Now it\u2019s time to create a CodeDeploy application. Switch to CodeDeploy console and select Create \u00a0New Application.<\/p>\n
\"wp-5\"<\/a><\/p>\n
Step \u2013 10 <\/strong>Fill the required details and attach the EC2 instance launched in the beginning.<\/p>\n
\"wp-6\"<\/a><\/p>\n
Step \u2013 11 <\/strong>Select the Deployment Configuration according to our requirement. Then click Create trigger<\/strong>, it will allow us to make configuration for AWS SNS (Simple Notification Services).<\/p>\n
\"wp-7\"<\/a><\/p>\n
 <\/p>\n
Step \u2013 12 <\/strong>Assign the Trigger name and Events we want to trigger. Then select the SNS topic for getting alerts of your deployment.<\/p>\n
\"wp-8\"<\/a><\/p>\n
Step \u2013 13 <\/strong>Select the Service-Role\u00a0<\/strong>for deployment. Then click Create Application <\/strong>and our application will be ready.<\/p>\n
\"wp-9\"<\/a><\/p>\n
Step \u2013 14 <\/strong>Navigate to AWS CodePipeline, where we can create a pipeline. Give a name to pipeline then click Next step.<\/strong><\/p>\n
\"wp-10\"<\/a><\/p>\n
Step \u201315 <\/strong>Select the Source provider as AWS CodeCommit <\/strong>\u00a0and fill the required details.<\/p>\n
\"wp-11\"<\/a><\/p>\n
Step -16 <\/strong>Select Deployment provider as AWS CodeDeploy <\/strong>and fill the required fields.<\/p>\n
\"wp-12\"<\/a><\/p>\n
Step \u2013 17 <\/strong>Select the Role name as AWS-CodePipeline-Service<\/strong> and then click Next step<\/strong>. It will navigate us to the review page, after reviewing details click Create Pipeline.<\/strong> We will get a pipeline created.<\/p>\n
\"wp-13\"<\/a><\/p>\n
We will get three stages of the deployment, namely No executions yet<\/strong>, In Progress<\/strong>, Succeeded<\/strong> or Failed<\/strong>.<\/p>\n
\"wp-14\"<\/a>\"wp-15\"<\/a>\"wp-16\"<\/a><\/p>\n
 <\/p>\n
1st<\/sup> Output<\/strong><\/p>\n
Now paste the Public IP of EC2 in browser.<\/p>\n
We will get output as database error connection<\/strong>. As in the wp-config.php<\/strong> database is mentioned as local.\"wp-17\"<\/a><\/p>\n
Now, change \u2018DB_HOST\u2019 from local to RDS by providing the end-point of RDS in wp-config.php<\/strong>. Then commit and push back to repo.<\/p>\n
Navigate to CodePipeline then click Release change. <\/strong>Wait for the Deployment to be succeeded. Paste the Public IP of the EC2 in browser.<\/p>\n
2nd<\/sup> Output<\/strong><\/p>\n
We will see WordPress installation page.<\/p>\n
\"wp-18\"<\/a><\/p>\n
 <\/p>\n
In short, we can say that AWS Codepipeline allows you to deploy WordPress on multiple servers without any downtime. Whenever we make changes to the configuration according to requirement, AWS Codepipeline lets you to release the change in no time.<\/p>\n
In case of any questions, please feel free to post your comments. You could also share your experience installing WordPress using AWS Codepipeline here.<\/p>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n","protected":false},"author":219,"featured_media":0,"parent":0,"comment_status":"open","ping_status":"open","template":"","blog_category":[3606,3607,3624],"user_email":"prarthitm@cloudthat.com","published_by":"324","primary-authors":"","secondary-authors":"","acf":[],"_links":{"self":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/4716"}],"collection":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/types\/blog"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/users\/219"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/comments?post=4716"}],"version-history":[{"count":1,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/4716\/revisions"}],"predecessor-version":[{"id":46094,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/4716\/revisions\/46094"}],"wp:attachment":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/media?parent=4716"}],"wp:term":[{"taxonomy":"blog_category","embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog_category?post=4716"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}