WordPress Certified by Bitnami and Automattic
Bitnami by VMware | 6.7.1-7-r08 on Debian 12Linux/Unix, Debian 12 - 64-bit Amazon Machine Image (AMI)
Too Complicated to Get Up and Running
People migrating to AWS from other hosting platforms are likely used to one-click installs of Wordpress from cPanel and other hosting management solutions. Just getting things up and running with an instance, security groups, elastic IP, and Route53 DNS "stuff" is a steep learning curve. Discovering that the Wordpress installation is not in the root directory of the domain and that one has to jump through a lot of hoops in order to get the thing working just adds to the frustration.
I ended up un-installing the instance and went with the YAPIXX instance from Oblaksoft because it is already connected to Amazon's S3 storage for hosting media files with the WP2Cloud plugin and the only extra step in addition to a typical one-click Wordpress install was adding three lines of authorization to actually get the EC2 server to talk with the S3 storage platform. That and firing up the typical security group, elastic ip, and tweaking a file to allow SFTP access to the server files for editing.
- Leave a Comment |
- Mark review as helpful
The default password doesn't work
I installed the Wordpress for Bitnami instance and followed all instructions. Just one problem - I can't login to the wordpress application. Everything I've tried has failed. The 'user' + the password from the System log just isn't right for some reason...
Terrible in terms of instructions to newbies
I will put it upfront that I am not a linux guy and also that I am new to AMI. So all the negatives here might not (or might) be BitNami's fault. But I did have my own WP installer manually setup in AWS using EC2, until something went wrong and everything went kaput. I tried BitNami thinking that the installation hurdles might be reduced.
I faced no issues in getting the AMI installed. But I faced several while trying to configure the final url (mainly) and in accessing phpmyadmin (I managed to do this). I tried going through BitNami documentation and even researched a few sites (mostly this was about updateip --appurl).
I think the biggest issue for me was that the structure of the directories is not at all similar to what I got when I had configured WP manually in EC2. Maybe this is expected, but I just couldn't overcome modifying the final url (even after managing to modify wp-config.php)!
Strangely I was charged $1 after installing the AMI. I have raised a ticket and am awaiting to see why this happened. But overall I think I wasted half a day in trying to tune this AMI according to my taste.
Useless
Since wordpress gets installed in yourdomain.com/wordpress it's completely useless and looks very unprofessional. I'm installing wordpress manually instead of wasting time on this.