{"id":316,"date":"2017-11-07T11:48:16","date_gmt":"2017-11-07T06:18:16","guid":{"rendered":"https:\/\/www.nocturnalknight.com\/?p=316"},"modified":"2017-11-07T11:48:16","modified_gmt":"2017-11-07T06:18:16","slug":"devops-post-series-1-how-to-install-and-configure-lamp-on-aws-ec2","status":"publish","type":"post","link":"https:\/\/nocturnalknight.com\/?p=316","title":{"rendered":"DevOps Post Series : 1, How to install and configure LAMP on AWS EC2"},"content":{"rendered":"

In this #DevOps centric series of blog posts, I will write about some of the interesting yet common problems and their solutions or quick guides and how-tos. This is the result of setting up a new #Datacenter setup for the #Startup I am working.
\n 
\nIn this post, I will assume that you have already launched an EC2 instance type with the operating system of your choice. Generally, Amazon Linux<\/a> (based on RedHat\/CentOS) or Ubuntu<\/a> is the preferred OS of choice. In case you prefer an exotic flavour of Linux, which does not support either the rpm\/yum(RHEL\/CentOS\/Fedora\/AMI) or apt (Debian\/Ubuntu and derivatives)\u00a0 this article may not be of much use to you.<\/p>\n

    \n
  1. Connect to your instance – Use the private key you downloaded during the ec2 launch.\n
      \n
    1. If you’re in Linux or Mac – use the following by replacing it with your private key name and instance’s public dns –\u00a0<\/code> ssh -i \"loginserver.\"root@ec2-xx-xx-xx-xx.compute-1.amazonaws.com <\/strong><\/code><\/strong><\/em><\/li>\n
    2. If you’ve launched an Amazon Linux, use “ec2-user” instead of “root”<\/li>\n
    3. If you’ve launched an Ubuntu Linux, use “ubuntu” instead of “root”<\/li>\n
    4. another important thing is to ensure that the private key has 0400 privilege and it is “owned” by the “User” as who you’ll execute the ssh connection.<\/li>\n<\/ol>\n<\/li>\n
    5. Update your package manager\n
        \n
      1. Amazon Linux : sudo yum update<\/strong><\/em><\/li>\n
      2. Ubuntu Linux: sudo apt-get update<\/strong><\/em><\/li>\n<\/ol>\n<\/li>\n
      3. Tools & Utils (Optional\/Personal Preference) I normally prefer to have a couple of tools installed in the server for quick-hacks\/edits, monitoring etc.\n
          \n
        1. Amazon Linux :<\/code> sudo yum install -y mc nano tree multitail git lynx
          \n<\/strong><\/em><\/strong><\/code><\/li>\n
        2. Ubuntu Linux: <\/code>sudo apt-get -y mc nano tree multitail git\u00a0 lynx<\/em><\/strong><\/code><\/code><\/strong>\n
            \n
          1. For details on the above-mentioned tools, refer the bottom of the article.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n
          2. LAMP Server\n
              \n
            1. Amazon Linux :<\/code>sudo yum install -y httpd24 php70 mysql56-server php70-mysqlnd mysql56-client<\/strong><\/code><\/li>\n
            2. Ubuntu Linux:\u00a0sudo apt-get install mysql-client-core-5.6 mysql-server-core-5.6 apache2 php libapache2-mod-php php-mcrypt php-mysql<\/strong><\/code>\n
                \n
              1. Your operating system will start to download and install the specified software, as for MySQL, you will be prompted for a root password. After installation, I strongly recommend you to run\u00a0mysql_secure_installation<\/code><\/strong><\/span> and proceed with the onscreen instructions.<\/li>\n
              2. Some of the critical things to do are remove the “test” db, remove access to \"root\"@\"%\"<\/code>, <\/strong><\/strong>others are optional.<\/li>\n
              3. The optional steps are,\n
                  \n
                1. remove the anonymous user accounts.<\/li>\n
                2. disable the remote root login.<\/li>\n
                3. reload the privilege tables and save your changes.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n
                4. Configuration and other dependencies\n
                    \n
                  1. Amazon Linux :\n
                    sudo<\/span> yum<\/span> install<\/span> php70-mbstring<\/span>.x86_64<\/span> php70-zip<\/span>.x86_64 composer node<\/span> -y<\/span><\/code><\/strong><\/code><\/pre>\n<\/li>\n
                  2. Ubuntu replace yum install with apt0get install<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
                    Finally, restart the services and off you go. You have successfully installed LAMP server in EC2. Now, go to your browser and enter the publicDNS of the ec2 instance and you should be able to see the default apache page.\u00a0 If you get either a timeout or not found error, it may mean you have to configure the security group accordingly. You should “ALLOW” port 80\/443 (http\/Https) in the security group.
                    \n\"\"<\/a>
                    \n                    \"\"<\/a>
                    \n 
                    \n 
                    \n 
                    \n 
                    \n 
                    \n <\/p>\n","protected":false},"excerpt":{"rendered":"
                    In this #DevOps centric series of blog posts, I will write about some of the interesting yet common problems and their solutions or quick guides and how-tos. This is the result of setting up a new #Datacenter setup for the #Startup I am working.   In this post, I will assume that you have already … <\/p>\n
                     Read More  Read More<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[1],"tags":[276,286,491],"class_list":["post-316","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-datacenter","tag-devops","tag-startup"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t