Infrastructure as Code (IaC) is the practice of describing servers, networks and cloud services in version-controlled files. Environments are then created and changed by running that code rather than by clicking through a console.
Policy as code means writing security, compliance and operational rules as machine-readable code that tools check automatically in pipelines and at runtime. Policies are versioned, reviewed and tested like application code.
Terraform is an infrastructure-as-code tool that lets teams define cloud and on-premises resources in declarative configuration files. It then plans and applies the changes needed to make reality match.
CI/CD is the practice of building and testing every code change automatically, then releasing changes that pass through a repeatable pipeline. It shortens the gap between writing code and running it in production.
Cloud architects design how systems run in the cloud; cloud engineers build and operate them. The architect owns the design decisions across the estate, and the engineer turns them into working environments.
A cloud engineer builds, configures and runs an organisation's infrastructure on cloud platforms such as AWS, Azure or Google Cloud. They keep environments working, secure and cost-controlled, so teams usually hire one as their cloud estate grows.
Cloud security posture management (CSPM) continuously checks cloud accounts for risky misconfigurations and drift from security policy. It then helps teams prioritise and fix what it finds.
A clear proven process, that delivers
You've seen our ideas - now go deeper.
Discover more insights, guides, and engineering practice.