<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cfn-lint on Mysterious Code - Senior AWS, DevOps &amp; security engineering</title><link>https://mysteriouscode.com/blog/series/cfn-lint/</link><description>Recent content in cfn-lint on Mysterious Code - Senior AWS, DevOps &amp; security engineering</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sat, 27 Jun 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://mysteriouscode.com/blog/series/cfn-lint/index.xml" rel="self" type="application/rss+xml"/><item><title>Multiplatform docker images for cfn-lint (and a v1.52 schema fix)</title><link>https://mysteriouscode.com/blog/multiplatform-docker-images-for-cfn-lint-and-a-v1.52-schema-fix/</link><pubDate>Sat, 27 Jun 2026 09:00:00 +0000</pubDate><guid>https://mysteriouscode.com/blog/multiplatform-docker-images-for-cfn-lint-and-a-v1.52-schema-fix/</guid><description>&lt;p&gt;A while back we wrote about our &lt;a href="https://mysteriouscode.com/blog/automatically-updated-docker-image-for-cfn-lint/"&gt;automatically updated docker image for cfn-lint&lt;/a&gt; -
a public, daily-rebuilt image for &lt;a href="https://github.com/aws-cloudformation/cfn-lint"&gt;cfn-lint&lt;/a&gt; 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.&lt;/p&gt;</description></item><item><title>Automatically updated docker image for cfn-lint</title><link>https://mysteriouscode.com/blog/automatically-updated-docker-image-for-cfn-lint/</link><pubDate>Thu, 18 Apr 2024 15:00:00 +0000</pubDate><guid>https://mysteriouscode.com/blog/automatically-updated-docker-image-for-cfn-lint/</guid><description>&lt;p&gt;If you&amp;rsquo;re using CloudFormation, you probably know about &lt;a href="https://github.com/aws-cloudformation/cfn-lint"&gt;cfn-lint&lt;/a&gt; - a
linting tool created by the CloudFormation team to validate templates against the schema and best practices. Validating
each template before deployment is in itself actually
&lt;a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/best-practices.html#validate"&gt;considered a best practice by AWS&lt;/a&gt;.
However, simply using &lt;code&gt;validate-template&lt;/code&gt; in the Console or CLI
&lt;a href="https://mysteriouscode.com/blog/how-to-validate-cloudformation-template-with-aws-cli/"&gt;only validates the basic syntax of the template&lt;/a&gt;,
not the actual contents and resource specification. That&amp;rsquo;s where using a linter like &lt;a href="https://github.com/aws-cloudformation/cfn-lint"&gt;cfn-lint&lt;/a&gt;
can be helpful to make sure you&amp;rsquo;re not making any obvious mistakes or going against best practices in your resources.&lt;/p&gt;
&lt;p&gt;You can use &lt;code&gt;cfn-lint&lt;/code&gt; in a number of ways during development, including simply within command-line, using git pre-commit
hooks or as a plugin to your IDE. All those options, while helpful in day-to-day work, do not establish code quality
standards for your overall codebase. To do that, it&amp;rsquo;s ideal to include linting as part of CI/CD pipeline and/or
pull/merge-requests approval process.&lt;/p&gt;
&lt;p&gt;That is where you can come across a hurdle: &lt;a href="https://github.com/aws-cloudformation/cfn-lint/issues/1025"&gt;cfn-lint does not have an official, up-to-date docker image&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>