How do you explain cloud technology to a person who is just entering IT? Start with the history. The terms can wait. That is how I came up with a comic about AWS CloudFormation, in which I explain everything through a doghouse. CloudFormation is a service that deploys cloud infrastructure using templates in JSON or YAML format.

I am Dmytro Ivanov, a Senior DevOps / Cloud Platform Engineer, in IT since 2014 and a graduate of Hillel IT School. In this column, I will tell how I went from a junior engineer to DevOps, why I took up CloudFormation, and how a work topic turned into an educational project.

My path: from a nerd to DevOps

By education, I am an environmental engineer. I entered IT from the very bottom, as an entry-level engineer. Then came first- and second-line support, system administration, and, eventually, DevOps. I went through this path like the OSI model, from the bottom up: from hardware and the network to the application. That is why today I see the product lifecycle as a whole, from commit to production.

Java was there too. On the second track, I was learning it on my own in parallel, using the Head First Java book, without any programming experience. Then I completed the Introduction Java and Java Elementary courses at Hillel IT School (now these are Java Basic and Java Pro). I searched for my first developer job for almost a year and finally received an offer as a Junior Java developer.

But then my path led me into infrastructure. At my first DevOps job, I got acquainted with Jenkins: I wrote job-dsl and pipelines in Groovy. Here Java came in handy again, because Groovy runs on the JVM. I worked with bare metal: migrated a monolith into microservices on docker-compose, set up an Ansible host for staging, administered and updated GitLab with runners, maintained CI/CD. For about four years I have been working with AWS in production, of which about two — with a focus on DevSecOps.

The development background hasn't disappeared. On the last project, I made architectural decisions together with a team of five engineers. I did code reviews together with Claude: I set up skills and agents in Claude Code for this.

Why CloudFormation specifically

The topic was suggested by work. I published products on AWS Marketplace three times and took the company through the AWS Foundational Technical Review (FTR) to AWS Partner status. In the first two products, CloudFormation was at the center of AWS's reviews: the client deployed the infrastructure in their own account using our template. We published the third as SaaS: we kept the infrastructure in-house on Terraform, and clients simply used the application.

After the first successful publication, I settled on a topic. After the second one, I finally decided to write specifically about CloudFormation.

A doghouse instead of terms

To someone who writes templates every day, CloudFormation is obvious. To a beginner, "infrastructure as code" and "stack" sound like incantations.

Imagine you're building a doghouse. You could explain to the carpenter every time where the walls are, where the roof is, and where the entrance is. Or you could draw a blueprint once, and they'll build even ten identical doghouses from it. In CloudFormation, such a blueprint is a template. You describe which resources are needed, and AWS creates, updates, and deletes them itself along with the stack.

The analogy is not perfect, but it conveys the main point: first the idea, then the syntax.

A year and a half for theory

I had long wanted to create my own course, but I couldn't choose a topic or format. When the topic was found, the format came on its own — a comic. You read it as a story, not as documentation.

The theoretical part took about a year and a half with breaks. I wrote in simple language and added pseudocode examples. The hardest thing was to establish the order: where to start, when to introduce a new concept, and which example to place next to it.

What next

The next step is the practical part with step-by-step videos: from a paper template to a stack in AWS.

While she waits. Right now I am looking for a new job, and time is going there. When this issue is resolved, I will return to the video.

The theoretical part is already available: the comic is posted in my LinkedIn post. If you find the topic interesting, write in the comments — this determines how quickly the second part will appear.