- Installing drupal on aws ec2 using command line how to#
- Installing drupal on aws ec2 using command line install#
CREATE USER drupaluser IDENTIFIED BY 'password' Create Database and UserĬreate database CREATE DATABASE drupaldb Ĭreate a drupal user. Now you will be able to access PHPMyAdmin over the browser by appending phpmyadmin to the ip as shown below.
Restart apache2 sudo service apache2 restart Open /etc/apache2/nf and add the following at the end of the line.
Installing drupal on aws ec2 using command line install#
Verify MySQL server status sudo service mysql status Install PHPMyAdmin sudo apt-get install phpmyadmin You should get a default apache page on your browser.Ĥ. Verify the Apache installation by visiting the public IP of your instance.
Installing drupal on aws ec2 using command line how to#
How to connect EC2 instance using putty Install LAMP Stackġ. You can follow this tutorial to connect to the instance using putty. If you are setting up SSL in future, you might need to add 443 as well. In our case, we would require port 80 and 22. How to Spin Up an Ec2 Instance Add Relevant Security GroupsĪdd the relevant port in the ec2 instance security group. Follow this tutorial if you haven’t done that before. Spinning up an EC2 instance is really easy. To setup Drupal on an EC2 instance, you need the following on the server.įollow the guides given below to set up a working Drupal installation. If you need help in deploying Drupal in HA mode, you can mail us at Install and Setup Drupal on Amazon EC2 For high traffic websites, it is advised to have a High Availability architecture with autoscaling and dedicated database instances. This is a standalone installation with Drupal and database in a single server. In this guide, I will explain how to install and setup Drupal on amazon ec2 ubuntu 14.04 server. # access here, or in any related virtual host. # your system is serving content from a sub-directory in /srv you must allow # the latter may be used for local directories served by the web server. # The former is used by web applications packaged in Debian, # not allow access to the root filesystem outside of /usr/share and /var/www. # Sets the default security model of the Apache2 HTTPD server. Nice to see you figured it out, but you should not put that configuration on the root directory.īelow is a snippet from Ubuntu's nf that explains a lot. This small and innocent mis-advice cost me hours of banging my head against the desk. So the unfortunate misinformation that I had adopted from various forum discussions on the topic was the command "sudo service httpd start", which was instructed somewhere in some discussion, and I took the advice at face value. This did the trick: Apache stopped and refused to restart, and gave the thank-you-so-helpful error message again. Then inspiration hit me: I am running the wrong command, I really should be saying "sudo service httpd restart". I got the message "Starting httpd:", no error messages, and Clean URLs still functioned. To investigate this mystery, I restored the above-mentioned syntax error into nf, and ran the command "sudo service httpd start". The weird part of this story is, why didn't I get these thank-you-so-helpful error messages yesterday, when having the same untouched version of nf, and running the same command "sudo service httpd start"? It also told the precise line numbers, and helpfully suggested that I fail to close the Directory tag, so I went to check, and was easily able to correct the obvious mistake: Īfter this fix, Apache started OK, and Drupal allowed me to enable Clean URLs, and we have been living happily ever since. Apache was not running, and refused to be started, complaining of syntax errors in nf. Today as I woke up in the morning, my Drupal website on AWS was completely down. PROBLEM SOLVED - what a journey in darkness this has been.
0 kommentar(er)
