AWS

We hit a frustrating issue recently while building PHP images in AWS CodeBuild: composer install started failing, often, with an HTTP/2 400 from codeload.github.com while downloading a package archive. The package that failed changed from run to run, and the same Dockerfile and composer.lock that broke in one pipeline built cleanly in another. The short version is that this is GitHub wobbling rather than anything wrong in your project, that the same failure has come and gone for years, and that the usual environment-variable fixes only take the edge off. If your deployments run composer install, here is what is actually going on and how to stop it taking your builds down.

Validating an IaC template before you hand it to CloudFormation is one of the cheapest ways to avoid the dreaded UPDATE_ROLLBACK_IN_PROGRESS. You can catch a lot without ever creating a stack - but only if you understand what the tool you use actually checks. Here are the two we usually use, and where one stops and the other takes over.

A while back we wrote about our automatically updated docker image for cfn-lint - a public, daily-rebuilt image for cfn-lint that fills the gap left by the lack of an official one. Two changes have just landed in that build, and both are worth a few words: the images are now multiplatform, and we have fixed a problem that, from cfn-lint v1.52.0 onwards, left the image unable to recognise any resources.

We’re excited to announce that Mysterious Code will be part of the Cloud & AI Infrastructure event at Tech Show London 2025!

As a member of the AWS Public Sector Partner Program, Mysterious Code Ltd will leverage its expertise to empower government, education and nonprofit entities with secure, scalable, and compliant cloud solutions built on AWS infrastructure. By combining AWS’s industry-leading cloud platform with Mysterious Code’s specialized knowledge and experience, public sector customers can expect enhanced capabilities in areas such as data security, compliance, and cost optimization.