I'm using the default configuration of this Drupal Amazon AMI, from this project http://drupal.org/project/ec2ami i have followed the steps of this tutorial http://drupal.org/node/15365 But I'm still not able to make CLEAN URL works. please i need some help of the community on this .. thank you very much,. AMI ID: ami-2a8a6d43

The AMI includes.

* Fedora Core 8 Linux
* Apache 2.2.9
* PHP 5.2.6
* MySQL 5.0.45
* Drupal Installer for any version of your choice ( u have to install 5.18 v. then upgrade to 6.12 to make it work)

I installed 5.18 drupal version then upgrade to 6.12 Drupal version, My site is working fine in SC3 except clean url

any one can help me to make Clean URL work?

Comments

snext’s picture

Having the same general issue with Clean URLs for Drupal in EC2. Were you able to figure it out?

derekahmedzai’s picture

Just in case someone else is having this problem:

  • edit /etc/httpd/conf/httpd.conf
  • Under <Directory /var/www/html>
    change AllowOverride None to AllowOverride All

This tells Apache to process Drupal's .htaccess file.

tanzeel’s picture

It worked for me :) Thank you very much.

Thank you,
Tanzeel

margaux’s picture

Perfect. Thanks from me, too!

vegantriathlete’s picture

Note: This AMI just loads Ubuntu.

You can follow the steps at: How to Forge to see how to set up the rest.

I'm using RDS, so I didn't install the mySQL server. I also didn't install phpMyAdmin.

I did install apache2, mysql-client-core-5.5, php5, libapache2-mod-php5, php5-mysql, php5-curl, php5-gd, php-pear, php5-mcrypt, php5-xmlrpc and php5-xsl.

php-pear is handy so that you can use

pear channel-discover pear.drush.org
pear install drush/drush

to install drush :-)


The way that apt-get install apache2 sets things up, you will need to modify:

/etc/apache2/sites-enabled/000-default

(/etc/apache2/apache2.conf does an Include sites-enabled/)

keywords: Ubuntu 12.04, Amazon, AWS, EC2, AMI, Clean URLs

vegantriathlete’s picture

I'm wondering if since we have access to the server configuration it makes more sense to NOT be allowing .htaccess to override things. Would it be better for performance if we just put the necessary things inside of httpd.conf (or whatever the proper main server configuration file is for that setup, such as apache2.conf or one of the sites-enabled/ files)?

jordan8037310’s picture