Bitnami wordpress stack on aws
- #BITNAMI WORDPRESS STACK ON AWS INSTALL#
- #BITNAMI WORDPRESS STACK ON AWS UPDATE#
- #BITNAMI WORDPRESS STACK ON AWS FREE#
It’s up to you, but look carefully for the ‘automated snapshot’ checkbox and enabled it if you want peace of mind at a small additional monthly cost.īe sure to choose the WordPress Stack. Unless you know better, match the new instance type to the old one.
The only recommendations here are that the instance is large enough to hold the existing system. Create a New Lightsail Bitnami WordPress Instance
#BITNAMI WORDPRESS STACK ON AWS FREE#
This makes it much easier, and free from DNS updates-to move between Lightsail instances, as we’re about to do.Ĭlick to manage your instance from the Lightsail dashboard then the networking tab then click the ‘create static IP’ button. With a static IP you can then point your domain’s A record to the IP address. Static IP addresses are free as long as they are assigned to an instance. With Lightsail you have the choice of assigning a static IP to your instance. Confirm the existing instance has a static IP The Lightsail service doesn’t immediately start offering new PHP versions when they are made available, and so you may need to wait on the Lightsail PHP versions on offer being updated before you continue with this process. Confirm a new Lightsail instance will be created with a high enough version of PHPīefore you get started, it’s worth you confirming that a new AWS Lightsail instance can be created with a PHP version high enough to resolve the message displayed in WordPress or a version suitable for your own needs. I take no responsibility for you not checking my workings before you use it yourself. Always back up everything before you start. Note: These steps were accurate at the time I wrote this guide.
#BITNAMI WORDPRESS STACK ON AWS INSTALL#
Install Let’s Encrypt ready for SSL creation later.Create a new Lightsail Bitnami WordPress instance.Confirm the existing instance has a static IP.Confirm the new Lightsail instances will be created with a PHP version high enough to resolve the WordPress message or the version of PHP you require for your own usage.
#BITNAMI WORDPRESS STACK ON AWS UPDATE#
There are a few steps to this update which I’ll run through below, but they boil down to something like: It would be nice if all this was possible by taking a snapshot and using it as the basis for a new instance, but sadly that isn’t the case. I read a fair bit about my options, but after looking at the choices I decided the best thing was to do an export and import onto a new Lightsail instance. My version was old and not receiving security updates. Logging into the WordPress admin console a message is displayed which is telling me WordPress would prefer a newer version of PHP please. The LAMP option allows a competent PHP developer to run almost anything on Lightsail.īut after a while running the Lightsail VPS the setup is going to get stale, and because Bitnami bundles everything up, it’s not recommended to go poking around with only a few parts of it. The Bitnami integration allows you to choose from a whole set of Stacks to include upon setup. Click a few buttons and you have a powerful VPS with WordPress up and running for only a few dollars a month. This guidance will walk you though creating a new Lightsail instance with a newer version of PHP installed and moving everything over to it. NB: If you’re hoping for a way to click ‘update php’ or ‘use X version of PHP’ in Lightsail, it doesn’t (at time of writing) exist. Updated 11th May 2021 to confirm that snapshots cannot be used to update the PHP version of a Lightsail Bitnami instance. Updated 25th January 2021 to add an initial paragraph clarifying that you can’t ‘choose’ a PHP version on Lightsail and to further clarify that you must first check which version of PHP a new AWS Lightsail instance will be built with to confirm it will resolve the message being displayed in WordPress.
Thanks to Peter and Simon in the comments. Updated 27th September 2020 to consider restart of all services where restarting just apache isn’t enough, and also to share choice when it comes to import first vs SSL first as you may lose s.