Migrate messy Symfony site from a dying AWS instance to another AWS server

We have a (poorly built) website based on an outdated build of Symfony that's on a t2.2xlarge server, which is almost certainly more than it needs even though the code is spaghetti and hardly efficient. AWS has announced they will be retiring the hardware the site runs on. In fact it may self-destruct at almost any moment. Therefore, I need to move the site to a new instance. Very quickly. For reasons of cost I’d like to move the site to a smaller instance - logically it shouldn’t need a t.2.2xlarge and it’s costing a bucket of money I’d rather be saving toward a rebuild of the site on a new CMS at some point in the future. This project, however, is NOT to rebuild the entire site. I can’t afford that right now and in any case I haven’t finished spec’ing what’s required. Here's the hard part - the site has a mountain of images, and there are different kinds of images stored in different places, depending upon what they are. Images inline with the text entered in the CMS have one path, while images in the site galleries have another. If you take on this work, you'll need to migrate the code from one server to another, but then check that the images all load in the CMS and in the front end. Everyone who has ever worked on this code says it’s a mess. Testing is obviously hard because the Symfony version hasn't been updated in a long time. Some of the site features, like guest login etc, have never worked and we're not about to fix them now. Your scope of work: (1) backup all the existing data and code and upload it to an S3 bucket which I can get access to, (2) move the existing data and code to something more suitable for a small site than a t2.2xlarge server (3) test the site once it's on the new server and (4) identify whether there are services on the other servers that the site is dependent upon and (5) if there are dependencies, move whatever is on the other servers to the new server so we eventually just have one server and one DB, then (5) check that the SSL certificates from the old server still work on the new instance, then (6) test everything end to end again, per the sequence below. Your testing will involve: (1) check the site is up and running, (2) check you can edit a test article and publish it, (2) test that you can upload a new gallery image in the test article and that it will show in the front end, (3) test that you can delete the test article, (4) test that the gallery images for existing articles load in both the CMS admin console and the front end of the site (you may need to check 5-6 articles at random), (5) test that an image inserted inline with the text of the test entry will load, (4) test that We have plans to do a complete rebuild, but at the moment the site is costing me so much to run that I can't afford to do the actual rebuild, which involves a lot of work. So this scope of work is just to put the site on a smaller server and try to make it run reasonably well without breaking the bank. To do this, you'll need access to our AWS console, which I'll provide, plus access to the CMS back end. I have an older version of the code in a Github account but I'm not sure how useful that would be. Feel free to ask questions before placing a bid. Trust me, this is more work than it sounds. People offering to rebuild the thing in Wordpress or something else will be ignored. Yes, one day we’ll do that. But that’s not what we’re doing now.