Keywords: Joomla - AWS - How to - Upgrade
This may be more of a AWS question than Bitnami, but given AMIs need to be updated/migrated regularly, I'm hoping to find people with the expertise/experience.
I have a Bitnami Joomla instance that is running older PHP and apache versions, and I need to migrate things. I'm fine with creating a new instance and migrating data- it's the practicalities of doing with on a production site that I'd like guidance on.
My instance has an elastic IP and has a load balancer attached to it, and the domain DNS in turn points to that domain.
Once I have the migrated site working on the new instance IP, I need to:
1. Point the elastic IP at the new instance
2. Deregister the ELB from the old instance and register it to the new instance.
What is the exact ordering of steps, considering pausing/stopping instances and re-registering the ELB, and is there anything else I need to think about? I'm hoping this will be a well-trodden path for those of you who have a similar setup.
As an aside, given the update limitations, and requirement to migrate to update the stack, are Bitnami AMIs a sensible choice for production applications, or have people found a better approach?
Thanks in advance for your input.