Infrastructure-as-code makes cloud environments reproducible and auditable, but the automation that applies it typically holds the keys to every account. If its state files, templates, module sources or runner can be influenced by a broad group, the effective number of administrators is much larger than the list in your access policy. Organizations should treat the automation pipeline, its state storage and its module sources as privileged systems. In practice that means restricting who can change them, pinning external modules to reviewed versions, requiring human approval of production plans, and giving the automation separate, narrower roles per account rather than one identity that can change everything.