Wow, we’re nearly there: the long journey to migrate our sites off AWS and on to a new box.
We began hosting there in 2012 but the server—which appears to have had a single major update in 2016—was getting very old. In 2018 we began searching for someone who knew about migrations.
The work hadn’t been finished but both gentlemen wound up getting very occupied in their regular gigs, and it was another year before a good friend said he knew how to do it.
From that point, it was about finding a few hours here and there that worked with both our time zones.
I am deeply grateful to him because I know just how busy he got, both professionally and privately.
The sites are now all on to a new box, and not on AWS.
We were only on there to begin with because in 2012, we chose to host with a friend’s company. AWS was familiar turf for him, but I never understood it. It’s a mess of a website, with an incomprehensible interface. No wonder people have to do courses on it. You really need a professional computing qualification to understand it.
Whomever said computers would become easier to use in the future was dead wrong, as I have never seen such a maze of technobabble offered to consumers before. It’s not even that presentable.
My hosting friend soon was head-hunted and I was left to deal with AWS.
The fact is if AWS was even remotely comprehensible I might have been able to do the migration myself. I estimate that if it were anything like normal, each of the sites would have taken me about five hours to do. It would have all been over in a month in 2018. If I had a week off to just do this, I probably could have done it—if server software was how it was in 2005.
It’s little wonder, given the convoluted confusion that AWS is, that it took three years to find someone match-fit to tackle it. And even then it took several months.
A week in 2005, three years in 2022. I don’t call that progress.
I approached half a dozen techs who had experience in web hosting and serving environments, some of them with very major organizations. A few of them were even given the keys to SSH into the server. I think three of them were never heard from again. I can only surmise that they saw a Japanese girl with long hair in front of her face crawl out of a well when they Telnetted into the box.
Once my latest friend had set up the basics, I was even able to do a few migrations myself, and handled the static sites. I even got a couple of Wordpress ones done. He did the lion’s share, beginning with the most complex (Lucire and Autocade, plus the advertising server).
Tonight, he did the last two sites from the second AWS instance.
The first instance has been stopped. The second is still running in case DNS hasn’t updated for the last two sites. The database has also been stopped.
You probably wouldn’t ever hire me or this firm to deal with AWS and, as it turns out, there are quite a few techs out there, who do this as their full-time job, who also don’t know it.
I plan to terminate the instances and the database by mid-week and close my AWS account. Amazon can figure out what to do with the S3 boxes, VPC, Cloudwatch, Cloudfront, and all the other stuff which I have no idea about.
It’s going to be a good day, provided they haven’t made account closures as contemptible a process. Because it’s not the only thing contemptible about Amazon.
Speaking of technology, it looks like I’ll be sticking with Opera GX going forward. The bugs in Vivaldi persist, despite another bug-fixing update last week. Five years with one browser isn’t too bad, and probably one of the longer periods I’ve stuck with a single brand.