{"id":22,"date":"2011-03-17T12:38:50","date_gmt":"2011-03-17T19:38:50","guid":{"rendered":"https:\/\/www.alexkorn.com\/blog\/?p=22"},"modified":"2014-08-15T14:35:07","modified_gmt":"2014-08-15T21:35:07","slug":"getting-php-mysql-running-amazon-ec2","status":"publish","type":"post","link":"https:\/\/www.alexkorn.com\/blog\/2011\/03\/getting-php-mysql-running-amazon-ec2\/","title":{"rendered":"Getting PHP and MySQL running on Amazon EC2"},"content":{"rendered":"

\nDo you know nothing about Amazon Web Services (AWS) or Linux server administration, but want to get a PHP\/MySQL server set up on AWS? I was once like you, relying upon my web host to have PHP and MySQL installed and configured, so it was a bit daunting initially to work with AWS, but it’s actually rather simple. Read on and I’ll show you how to set up PHP and MySQL on one of Amazon’s free servers<\/a> step by step. You can have a functioning site up and running within half an hour.\n<\/p>\n

Amazon Web Services<\/h2>\n

\nFirst things first: Amazon Web Services has a ton of different products, but the one you want is Amazon Elastic Compute Cloud<\/a> (EC2<\/em>). Go there, and click “Sign Up for Amazon EC2”.\n<\/p>\n

\nOnce you’ve gotten that set up, go to the AWS Management Console<\/em><\/a>, and click on “Instances” in the Navigation panel. An Instance<\/em> is just a virtual server – so let’s create one! Click “Launch Instance” under “My Instances”, and select “Basic 64-bit Amazon Linux AMI”. On the Instance Details<\/em> phase, select “Micro” (which is Free tier eligible). Continue until you need to enter the “Name” – if you don’t know what else to call it, just use “Web\/DB server”.\n<\/p>\n

\nNext you create a Key Pair<\/em> – this will be the credentials you’ll use to SSH into the box. The instructions here should be fairly straightforward. Next is the Security Group<\/em>, which will be used to specify the firewall used for your instance. Feel free to use the default Group for now. Continue to the Review<\/em> phase and launch it!\n<\/p>\n

\nYou should now be able to SSH into your instance using your .pem file with ssh -i [FILE NAME].pem ec2-user@ec2-[IP ADDRESS].compute-1.amazonaws.com<\/code>. Alright, we’ve got a server up and running! However, you may notice that this server has very little installed on it. which php<\/code>? Nothing. which mysql<\/code>? The same. Let’s install some software.\n<\/p>\n

Configuring the Linux Server<\/h2>\n

\nBelow I’ll show you how to set up PHP and MySQL on the server. I’ve separated PHP and MySQL so that it’s easier to adapt this to having two instances<\/a>.\n<\/p>\n

PHP<\/h3>\n

\nFirst, the basics for PHP:\n<\/p>\n

\r\nsudo yum install php-mysql php php-xml php-mcrypt php-mbstring php-cli mysql httpd\r\n<\/pre>\n
\nPress ‘y’ for each of the prompts that shows up. Note that you’re logged in as ec2-user, so you need to sudo<\/em> all of these commands.\n<\/p>\n
\nYou should now be able to create and run a PHP test file. Next, let’s get MySQL up and running.\n<\/p>\n
MySQL server<\/h3>\n
\nFirst, install and begin running the server:\n<\/p>\n
\r\nsudo yum install mysql-server\r\nsudo \/etc\/init.d\/mysqld start\r\n<\/pre>\n
\nNext, set the root password. I’ve found this password generator<\/a> to be just dandy.\n<\/p>\n
\r\nmysqladmin -u root password '[PASSWORD]'\r\n<\/pre>\n
\nNow we set up two users for MySQL: the administrator, which you’ll use to create and modify tables; and the app user, which the app will use to query the DB (with more limited privileges). Log into MySQL as root<\/code> (mysql -u root -p<\/code>) and enter each of the following lines:\n<\/p>\n
\r\nCREATE DATABASE [DB NAME];\r\nCREATE USER '[DB NAME]_admin'@'localhost' IDENTIFIED BY '[ADMIN PASSWORD]';\r\nGRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER ON [DB NAME].* TO '[DB NAME]_admin'@'localhost';\r\nCREATE USER '[DB NAME]_user'@'localhost' IDENTIFIED BY '[USER PASSWORD]';\r\nGRANT SELECT, INSERT, UPDATE, DELETE ON [DB NAME].* TO '[DB NAME]_user'@'localhost';\r\n<\/pre>\n
\nYou may want to fine-tune your database settings further than this, but this is a good start.\n<\/p>\n
Make it web-accessible<\/h2>\n
\nWe now have PHP and MySQL running on the box, but cannot access it through a browser. We need to configure the web server and set up an Elastic IP<\/em>.\n<\/p>\n
Web Server<\/h3>\n
\nFirst, let’s create a test PHP file that will be accessed by the browser. Create directories so that you can put your file in \/opt\/app\/current<\/code>1<\/a><\/sup>. Make an index.php<\/code> file that contains whatever you want.\n<\/p>\n
\nIf you want to FTP transfer files to your server, you’ll want to give the ec2-user permissions to modify files in your web directory:\n<\/p>\n
sudo chown ec2-user \/opt\/app\/current<\/pre>\n
\nTo set up the web server, httpd<\/em>, we need to first modify its configuration file, located at \/etc\/httpd\/conf\/httpd.conf<\/code>. Open it up with vim<\/code>, emacs<\/code>, or your favorite text editor, and go to the bottom of the file. Here you’ll see a small section on the VirtualHost<\/em> (between <VirtualHost *:80><\/code> and <\/VirtualHost><\/code>). Uncomment it out and set DocumentRoot to \/opt\/app\/current<\/code>. Restart (or start) httpd<\/code>:\n<\/p>\n
\r\nsudo \/etc\/init.d\/httpd restart\r\n<\/pre>\n
Elastic IP<\/em> and Security Groups<\/em><\/h3>\n
\nIn the AWS Management Console<\/em>, click on “Elastic IPs”, then “Allocate New Address” under “Addresses”. Once the address is created, click on it, then “Associate Address”. Select the instance and associate it.\n<\/p>\n
\nNow click on “Security Groups” in the Navigation panel. Select the Security Group<\/em> that you used for the instance (probably the default one). Under the “Inbound” tab, add an HTTP rule (port 80). Click “Apply Rule Changes”, and you should now be able to access your website! In your browser, go to http:\/\/ec2-[IP ADDRESS].compute-1.amazonaws.com\/<\/code>, where the IP address is the Elastic IP<\/em> you made with periods replaced with hyphens.\n<\/p>\n
Hello World! or<\/span> Putting it all together<\/h2>\n
\nWe now have all the pieces we need to access MySQL from PHP and serve that to the browser-accessible website. So let’s log into mysql<\/code> and create a sample table:\n<\/p>\n
\r\nmysql -u [DB NAME]_admin -p\r\n[type password]\r\nmysql> use [DB NAME];\r\nmysql> CREATE TABLE test (message VARCHAR(255));\r\nmysql> INSERT INTO test (message) VALUES ('Hello world!');\r\n<\/pre>\n
\nNow modify your index.php file (\/opt\/app\/current\/index.php<\/code>) to be the following:\n<\/p>\n
\r\nquery(\"SELECT message FROM test;\");\r\n$row = $result->fetch_assoc();\r\necho $row['message'];\r\n?>\r\n<\/pre>\n
\nWe now have a fully functioning PHP and MySQL server!\n<\/p>\n
Taking it further<\/h2>\n
\nThat’s it for the basics, but there’s so much more that you can do now.\n<\/p>\n
PHPUnit<\/a><\/h3>\n
\r\nsudo pear upgrade\r\nsudo yum install php-pear\r\nsudo pear channel-discover pear.phpunit.de\r\nsudo pear channel-discover pear.symfony-project.com\r\nsudo pear channel-discover components.ez.no\r\nsudo pear install phpunit\/PHPUnit\r\n<\/pre>\n
phpMyAdmin<\/a><\/h3>\n
\nI’ve found it handy to set up an administration area for my sites using a different port on the same URL. Note that port 80 is the default for web traffic, but 8080 is also commonly used.\n<\/p>\n
\nCreate \/opt\/app\/admin<\/code>. Then, in httpd.conf<\/em>, add the line Listen 8080<\/code> after Listen 80<\/code> and add another VirtualHost<\/em> entry, using <VirtualHost *:8080><\/code> and pointing to the \/opt\/app\/admin<\/code> directory. Update your Security Group<\/em> to allow traffic over port 8080. Make sure to restart Apache and you should now be able to access your admin<\/em> folder through your browser at yourdomain.com:8080<\/code>.\n<\/p>\n
\nYou can then download phpMyAdmin into \/opt\/app\/admin\/pma<\/code> and unzip it. Using the [DB NAME]_admin<\/code> user, you can now manage your databases there through your browser.\n<\/p>\n
<\/a><\/p>\n
Using two Instances<\/em><\/h3>\n
\nIt can be very beneficial to performance to separate the web server and the DB server. To do this, you’ll need to set up two Instances<\/em>, one of which has the web server httpd<\/code> running and an Elastic IP<\/em>, and the other of which has the MySQL server mysqld<\/code> running.\n<\/p>\n
\nThey can use the same Security Group<\/em>, but you’ll have to add the MySQL rule (port 3066) for Inbound traffic to allow the servers to talk to each other.\n<\/p>\n
\nOn the web box, instead of using “localhost” as the MySQL host, use the Internal IP address of the MySQL box. On the DB box, set up your grant<\/em> permissions to allow from anywhere in '%.ec2.internal'<\/code> (or just from your IPs).\n<\/p>\n
Notes<\/h2>\n
<\/a><\/p>\n
    \n
  1. \n
    \n\/opt\/app\/current<\/code> is a Rails convention that I enjoy. What you should do is put your releases in \/opt\/app\/releases\/[release #]<\/code>, then have \/opt\/app\/current<\/code> be a symlink<\/code><\/a> to the current release.\n<\/p>\n
    \nAnother (much more) common standard is to put web-accessible code in \/var\/www\/html<\/code>. Feel free to put your HTML code wherever you want; just make sure to update httpd.conf<\/code> appropriately (and restart Apache).\n<\/p>\n
    ^ Back up<\/a><\/p>\n<\/li>\n<\/ol>\n
    \n
    \nThanks to Ryan Ausanka-Crues<\/a> at Palomino Labs<\/a> for help with this.<\/p>\n","protected":false},"excerpt":{"rendered":"
    Do you know nothing about Amazon Web Services (AWS) or Linux server administration, but want to get a PHP\/MySQL server set up on AWS? I was once like you, relying upon my web host to have PHP and MySQL installed and configured, so it was a bit daunting initially to work with AWS, but it’s […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,15,16],"tags":[12,26,13,17,14,6],"class_list":["post-22","post","type-post","status-publish","format-standard","hentry","category-aws","category-hosting","category-tutorials","tag-amazon","tag-apache","tag-ec2","tag-linux","tag-mysql","tag-php"],"_links":{"self":[{"href":"https:\/\/www.alexkorn.com\/blog\/wp-json\/wp\/v2\/posts\/22","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.alexkorn.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.alexkorn.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.alexkorn.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.alexkorn.com\/blog\/wp-json\/wp\/v2\/comments?post=22"}],"version-history":[{"count":0,"href":"https:\/\/www.alexkorn.com\/blog\/wp-json\/wp\/v2\/posts\/22\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.alexkorn.com\/blog\/wp-json\/wp\/v2\/media?parent=22"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.alexkorn.com\/blog\/wp-json\/wp\/v2\/categories?post=22"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.alexkorn.com\/blog\/wp-json\/wp\/v2\/tags?post=22"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}