laurenceshaw.net technical documents

Use of these resources represents your agreement to Australian © Copyright Laws and the general guidelines in our Terms of Use & Privacy Policy

These articles are not easy to follow and need IT skills to work through, but they show what must be done to use an EC2 instance with WordPress. No liability at all for use of this information.

Documents
date: 20 07 2020 bytes: 833462     axoncpn file: axoncpnid001-Amazon_S3FS_WordPress_CDN_Scripting_v2.pdf
date: 03 12 2020 bytes: 26922      axoncpn file: axoncpnid002-ip2location_installation.pdf
date: 03 12 2020 bytes: 39375      axoncpn file: axoncpnid003-section1-launch_configure_ec2_for_WordPress.pdf
date: 03 12 2020 bytes: 32779      axoncpn file: axoncpnid003-section2-configure_Linux2_for_WordPress.pdf
date: 03 12 2020 bytes: 50739      axoncpn file: axoncpnid003-section3-installing_HTTPD_MARIADB_PHP72.pdf
date: 03 12 2020 bytes: 65394      axoncpn file: axoncpnid004-Disaster-Recovery-Backups.pdf
date: 28 05 2021 bytes: 27350      axoncpn file: axoncpnid005_Install_EC2_Linux2_Php74.txt
date: 07 05 2021 bytes: 6313       axoncpn file: axoncpnid006-Amazon_SES_Microsoft_Exchange.txt

MODIFICATIONS

Article id-001:
The following should install s3fs rather than using git and make:
sudo amazon-linux-extras install epel
sudo yum install s3fs-fuse

Article id003: Linux
This is now replaced by Article id005 for PHP7.4

Article id-004:
I have had a lot of phpMyAdmin failures when importing SQL backups – never used to have the problem.
I may suggest making DR backups of each section of the tables – e.g. the WordPress tables, the plugin tables per plugin.
This would give ability to rebuild by omitting plugins that fail to re-install.