After a Magento upgrade, the mg3_catalogsearch_fulltext_scope1 table disappeared from the MySQL database of my Magento 2-based webshop. As a result, all product-related pages were returning HTTP 500 error code, and I could not create or update products in the admin panel.

Recently I got a question about Cloudfront where there were multiple backends and the asker wanted to bring everything under a single distribution. I then realized that AWS’s naming does not help much in this case. The different backends are called origins which is plausible if you consider that is the origin of the data. But then where to set up path-based routing? Exactly, that is (partially) what cache behaviors are good for.

Recently I got a question about how to set up a mechanism to automatically respond to a resource being marked as non-compliant by a Config Rule. AWS recently rolled out a feature for that, but it’s so new at the time of writing even Terraform had no support for it.

When a name is optional for a resource then, just like CloudFormation, Terraform will generate a random one when you deploy the stack. This makes it easy to deploy these resources and makes sure that you can safely deploy the same module multiple times.