• Looking to use Amazon Web Services (AWS) for hosting your next WordPress site but you’re not familiar with deploying AWS EC2 instances? We recommend that you use Amazon Lightsail. Amazon Lightsail extracts away a lot of the complexities around AWS and makes it simple to spin up virtual servers, while still using the same underlying AWS.
• If you followed my advice above, now would be the time to change your DNS records to point to the Lightsail nameservers (sub-step 3 of step 6 of the AWS Lightsail WordPress tutorial) — wait a few hours to make sure the DNS settings have propagated and then test out your domain and make sure it points to a page with the Bitnami banner in the.

Update:

AWS Lightsail is very fast, as long as you set it up properly. To improve the page loading speed for clients you need to use a CDN, so that copies of pages are stored at different locations around the world and the viewer gets a copy from the location closest to them.

I no longer use Bitnami on AWS LightSail due to the steps required to get sane application behaviour and performance are not worth it. Leaving this up for any searches leading here and will recommend for a similar level of serviced hosting, try DigitalOcean or Vultr.

Tired of clunkily updating a GitHub gist, herein lie my notes used when provisioning an AWS LightSail instance with Bitnami WordPress for quick migration/debugging of an existing user’s WordPress site.

• copy public key via the virtual terminal in AWS Console
• set a DNS entry to point dev domain to the instance’s IP
• access site at dev domain
• rm bitnami banner
  • sudo /opt/bitnami/apps/wordpress/bnconfig --disable_banner 1
  • sudo /opt/bitnami/ctlscript.sh restart apache
• SSH in using dev domain
• enable SSL
  • sudo mkdir /opt/bitnami/letsencrypt
  • cd /opt/bitnami/letsencrypt
  • sudo wget https://dl.eff.org/certbot-auto
  • sudo chmod a+x ./certbot-auto
  • sudo ./certbot-auto
  • sudo ./certbot-auto certonly --webroot -w /opt/bitnami/apps/wordpress/htdocs/ -d example.com
  • sudo ln -s /etc/letsencrypt/live/[DOMAIN]/fullchain.pem /opt/bitnami/apache2/conf/server.crt
  • sudo ln -s /etc/letsencrypt/live/[DOMAIN]/privkey.pem /opt/bitnami/apache2/conf/server.key
  • Make sure that the certificate file name and path is correct. If you receive an error that file already exists, use the below command to rename the files:
  • mv /opt/bitnami/apache2/conf/server.key /opt/bitnami/apache2/conf/serverkey.old
  • mv /opt/bitnami/apache2/conf/server.crt /opt/bitnami/apache2/conf/servercrt.old
  • sudo /opt/bitnami/ctlscript.sh restart apache
• adjust wp-config to use https
  • sed -i 's/http/https/' /opt/bitnami/apps/wordpress/htdocs/wp-config.php
  • sudo chown -R bitnami:daemon /opt/bitnami/apps/wordpress/htdocs/
• force https in top of file: /opt/bitnami/apps/wordpress/conf/httpd-prefix.conf
  • RewriteEngine On
  • RewriteCond %{HTTPS} !=on
  • RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]
• Restart server to enforce https
  • sudo /opt/bitnami/ctlscript.sh restart apache
• backup wp-config somewhere
  • sudo cp /opt/bitnami/apps/wordpress/htdocs/wp-config.php /opt/bitnami/apps/wordpress/wp-config-backup-randstring.php
• disable mod pagespeed
  • sudo vim /opt/bitnami/apache2/conf/pagespeed.conf
  • ModPagespeed on > ModPagespeed off
  • sudo /opt/bitnami/ctlscript.sh restart apache
• copy existing site’s files into WP dir
• backup existing wp-config
  • sudo cp /opt/bitnami/apps/wordpress/htdocs/wp-config.php /opt/bitnami/apps/wordpress/user-original-wp-config-backup-randstring.php
• restore Bitnami’s wp-config
• copy any custom define’s or code from existing wp-config
• import users DB
  • delete bitnami_wordpress
  • create bitnami_wordpress
  • import .sql
• rewrite any hard links within DB
  • sudo wp --allow-root search-replace 'OLD.domain.com' 'NEW.wp2static.com'
• change admin user email and pwd
  • sudo wp --allow-root user update 1 --user_pass='PASSWORD'
• rewrite any hard links within site (optional, careful of mailto links, etc)
  • find -name '*.css' -exec sed -i 's/OLD.domain.com/NEW.wp2static.com/g' {} +

• reset file permissions

  • sudo chown -R bitnami:daemon /opt/bitnami/apps/wordpress/htdocs/
  • sudo find /opt/bitnami/apps/wordpress/htdocs/ -type f -exec chmod 664 {} ;
  • sudo find /opt/bitnami/apps/wordpress/htdocs/ -type d -exec chmod 775 {} ;
  • also php-fpm restart sudo /opt/bitnami/ctlscript.sh restart php-fpm

• enable debugging

define( 'WP_DEBUG', true );

tailing WP logs

tail -f /opt/bitnami/apache2/logs/error_log

connect to db

mysql -u bn_wordpress -p bitnami_wordpress # and pwd from wp-config

check plugin options

select * from wp_options where option_name = 'wp-static-html-output-options' G;

• working_directory option can persist the old sever’s paths

Aws Lightsail Wordpress Email

modify PHP ini

• disable opcache
• disable mod pagespeed
• use development level error logging
• increase memory
• extend max execution time

sudo vim opt/bitnami/php/etc/php.ini

Basic Auth

less noisy error log

sudo echo 'ErrorLogFormat 'n '%M' n ' >> /opt/bitnami/apache2/conf/httpd.conf

^ needed re-rediting to affect the CR’s, look to fix

Scratch notes

Aws Lightsail Wordpress

• deal with (70007) The timeout specified has expired errors from proxy_fcgi:error:

Timeout 900 ->

in /opt/bitnami/apache2/conf/httpd.conf

import vim and tmux confs

Aws Lightsail Wordpress Https

curl https://gist.githubusercontent.com/leonstafford/6891b76aeaf43766dd52676d6bed1b08/raw/9979e28a9abf07af94b505d35ff9a4eb3da7cb9f/.tmux.conf --output ~/.tmux.conf

Aws Lightsail Wordpress Download

curl https://gist.githubusercontent.com/leonstafford/39333da3399adee7e88cb869b4685dff/raw/5e6e7b7fb834d996763da3d358d949d309691350/.vimrc --output ~/.vimrc

Aws Lightsail Wordpress Login

not working without additional domain verification overrides: - enable mail sending (consider Amazon has a limit for LightSail) not verified, erros with - sudo apt install sendmail - sudo vim opt/bitnami/php/etc/php.ini - uncomment sendmail_path = 'env -i /usr/sbin/sendmail -t -i' - sudo /opt/bitnami/ctlscript.sh restart apache