ClickOps means creating or changing infrastructure by manually navigating cloud interfaces. It can feel like the quickest route to a working server, but the clicks are hard to repeat accurately. section 9.6
Manual infrastructure changes can leave behind:
- Snowflake servers that are fragile and difficult to rebuild after a failure. section 9.6.1
- Mismatched servers when people repeat a long sequence of clicks at scale. section 9.6.1
- Configuration drift between environments as settings are manually tweaked. section 9.6.1
Infrastructure as Code offers a more repeatable alternative: describe the desired end state in a version-controlled blueprint, then let an engine determine the steps. ClickOps is imperative; IaC is declarative. section 9.6.2
A costly typo
During the 2017 AWS S3 outage, an engineer’s production command removed more servers than intended. The lesson is to use review and automated checks rather than rely on perfect human clicks or typing. section 9.9
Figure 9.8 Friends don't let friends type in production. The 2017 AWS S3 outage proved that human fingers are the most dangerous part of any architecture.

See the figure illustrating the production-typing lesson from the AWS S3 outage. section 9.9
