design-infrastructure

To generate secure Terraform and Docker artifacts with least privilege, this Skill produces hardened infrastructure designs featuring managed identity defaults, private networking, and rootless multi-stage Docker build guardrails.

CI/CD pipeline hardening for Azure and GCP works by enforcing managed identities, eliminating raw environment secrets via Key Vault retrieval, and validating Terraform drift during the deployment workflow.

Minimizing blast radius in multi-cloud IaC involves justifying Azure vs GCP placement, enforcing network isolation, and implementing remote locked Terraform backends with drift detection to contain failures.

Yes, you can use this to justify Azure versus GCP placement by evaluating cloud fluidity, analyzing storage behaviors, and ensuring deployment workflows maintain least privilege across the chosen provider.

Terraform state management requires a remote locked backend with drift detection to maintain infrastructure integrity, prevent concurrent modifications, and ensure deployment workflows remain predictable and secure.

Yes, you need managed identity and private endpoints to harden cloud delivery pipelines because they eliminate raw environment secrets and enforce network isolation, directly minimizing blast radius.