Blog Migration H-Eeeee-Double-Toothpicks And Why I Left #AWS

wordpress

Due to (technical) knowledge constraints I thought I overcame, I recently gave up hosting my blog with AWS. According to the conspiracy theorist inside my third-eye, I think the problem I had hosting at AWS was due to the fact that they couldn’t up-sell me and my lolly blog from being free-tier to being (insert $-amount) per month. Yeah, “free-tier” at AWS is only worth it if:

  • You don’t get many hits at your blog
  • You’re a webserver expert.

The only way AWS would help me with any problems was if I paid them for the help. In other words:

  • Free-tier web hosting at AWS is cool until you need even the slightest amount of help.

Now ain’t that suspicious? It’s especially suspicious when it’s obvious that a problem occurs not because of what I did but becuae of what AWS did which amounts to things being:

  • Suspicious.

But don’t get me wrong. I’m only blowing off some steam here. The problem I had with hosting my Worpress blog at AWS was solvable. I just didn’t know how to solve it–and something was telling me that if I’m gonna have to pay to have that amount of limited service, AWS isn’t for me.

The pseudo dream has always been to actually set up my own server at home and run my compulsive writing blog there. It’s really a rather simple thing to do. That’s what makes it extra frustrating that I couldn’t solve the problem at AWS. All one has to do is connect a home webserver to the outside world. For this you need the proper bandwidth. It’s no coincidence that we all can get high downloads speeds with our home Interent connections but only measely upload speeds. In Germania, as well endowed with phone lines and cable lines as the country is, I’m sure that the powers-that-be don’t want people to start hosting their corners of the internet at home. Indeed. And so. I constantly had the following error while hosting my blog on a Linux server at AWS:

  • “Error establishing a database connection”

As best I can tell this “error” is due to a mix-up between WordPress, which is my blog content management system, and AWS’s management of its server iterations. The mix-up or “error” occurs when one or all of the following happens while hosting a WordPress blog:

  • Free-tier blog gets too much traffic
  • AWS fiddles around with its systems and thereby forces changes to WordPress configuration files.

The thing is, I don’t feel like going that deep into all this technology krapp. It was actually a fun project a few years back when I went from 1und1 hosting to AWS. Installing Worpress on AWS was cool. But it’s now clear that free-tier doesn’t mean what you think it means. And that’s fine. I can deal with that. And I can even pay a couple of bucks a month to WordPress in the hope that all those database error messages are over.

We’ll see.

Rant on.

-t

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s