Excited to share #cloudformation crimes with friends today.

weirdly satisfying defeating esoteric #aws #cloudformation bugs

Is it even #InfrastructureAsCode if it doesn't track changes over time?

Some #infrastructure tools (#CloudFormation, #helm) adequately encapsulate deployable examples of working systems, but do not necessarily manage that infrastructure over its lifecycle.

My argument would be that it is most realistic to think of "infrastructure" as "the set of things deployed in my environment as they currently are." Any tool that makes it hard to keep that in code falls short.

#devops

The main reason you want to make sure you use CloudFormation is determinism.

The other reason is SDK calls *will* result in unexpected 429 status code responses so you always need to implement back off, retry, and failure on *every* call site.

Which is to say: SDK calls have poor determinism. Maybe you can do that better than the AWS CFN team but not on a long timeline.

#aws #cloudformation

I might've or might've not cried while doing this.
#aws #cloudformation :(

I might've or might've not cried while doing this.
#aws #CloudFormation :(

An introduction:

I spend the days wrangling my #DevOps team, writing #Cloudformation, dealing with #InfoSec, trying to #ShiftLeft our tech culture. In the past, worked in the transactional email space; faux #MSSQL #mySQL #DBA, hardware/#datacenter flunky, Citrix Netscaler admin.

In my personal time, #homelab, #3DPrinting, #pizza maker/consumer, #BBQ, #HomeAutomation, #PatientGamer, Japanese / #Rye #Whiskey enjoyer-er,

@felix_eckhardt #AWS would argue that #CloudFormation is #IaC - which would be JSON or YAML "code"?