AWS – Frank-Mich's Blog

Recipe: Migrating a WordPress Blog Over AWS Lightsail

Posted on 2024/01/152024/01/15 by Frank-Mich L'Heureux

The blog you are currently on used to be hosted on some Virtual Private Server. My hosting provider decided to quit the business and I had to leave. He kindly suggested that I look at AWS Lightsail as a migration option. I did, and this is where this blog is now hosted.

This blog is not new. It already had content. It also has customisations like plugins and themes. This post will focus on how to export your content and customisations from a former blog and import them on Lightsail. Its accuracy may vary depending on the level of customisation your blog has. Command line (CLI) experience is required.

Serverless: How to share the ids of an existing API Gateway

Posted on 2023/01/312023/01/31 by Frank-Mich L'Heureux

The serverless documentation indicates how to share the ids of an API Gateway, but the technique described there seems to work only for a new deployment. (In my case, following this technique created a 2nd empty API Gateway whose ids were shared, which was, unsurprisingly, not fulfilling my needs).

Here is how to do it for an existing deployment.

Minimize the size of lambdas by deleting boto3 from the deployment package

Posted on 2022/08/292022/08/30 by Frank-Mich L'Heureux

Last April, I wrote a post about managing boto3 in deployed packages. (See Minimizing the size of lambdas by avoiding having boto3 and its stubs in the deployment package). This approach works when all dependencies can be set in the development section.

But, what about when dependencies are required in production? For example, we recently had to deploy a lambda that depends on awswrangler. So the technique suggested in the previous post did not work. Here I will cover a different approach that allows to remove boto3 from the package to be deployed in the example context. It is however less flexible and based on a specific technology: serverless.

Minimizing the size of lambdas by avoiding having boto3 and its stubs in the deployment package

Posted on 2022/05/282022/11/16 by Frank-Mich L'Heureux

If you are having problems with AWS lambdas exceeding the 250MB limit, here is a tip that might help.

AWS marketplace and no longer supported instance types

Posted on 2018/02/26 by Frank-Mich L'Heureux

I’ve been trying and trying to launch a Neo4j instance on the marketplace without success. It always gave me the nice “success” message, but when I went to the EC2 console: nothing!

A nice green “success” message even though it doesn’t work.

I finally decided to do it the hard way: manually. First step: select an instance type. I immediately try to select the same low cost instance I had picked in the marketplace (m3.medium) and to my surprise that type wasn’t there.

Instance type selection as per the Neo4j marketplace page.

Adding 1 + 1, I went back to the market place and tried with an instance type that still exists: m4.large… success!

So I don’t know who is to blame here, but here are my 2 questions to the internet:

Why do we get the success message even though it doesn’t work?
Why are unsupported instance types offered in the market place?