Keywords: General - Amazon Web Services - Technical issue - Upgrade
- Running SilverStripe Certified by Bitnami on AWS, version 3.1.13.
- There's a general security notification encouraging upgrade for SegmentSmack, L1 Terminal Fault and Foreshadow amongst others. Looks like a good time to upgrade SilverStripe anyway.
SilverStripe publishes an extensive upgrade guide at https://docs.silverstripe.org/en/4/upgrading/ , and I expect this to be useful. It does however make assumptions about how might have supplied the remainder of the stack yourself - e.g. PHP wanting upgrade from 5.x to 7.1.x, Composer upgrades etc. In SilverStripe/Bitnami on AWS of course the entire stack is provided in the image - this means there is a custom PHP installation/location etc.
This isn't a major problem and there's likely a reasonable upgrade path, but you have to bear in mind the custom PHP install etc. when upgrading. The SilverStripe documentation assumes an in-place upgrade.
I was wondering if there was a high-level recommendation on how to achieve this for Bitnami SilverStripe. For example, a same-instance upgrade might not be the simplest path and could result in a less maintainable instance. There might for example be a new-instance-create (4.2.1-0-r35), restore-(3.1.13)-and-upgrade path which would involve less risk and result in a cleaner install.
Is there any information, documentation or advice on the likely best approach here?
I have had one practice attempt (on a duplicate instance) of following the SilverStripe in-place upgrade process (of 3.1.13), and am now planning on trying a new-4.2.1-0-r35-instance import/upgrade.