Section 15.140 Infrastructure as Code (IaC) Flashcards
Objective 3.1 Compare and contrast security implications of different architecture models. Objectives 4.1 Given a scenario, apply common security techniques to computing resources
Infrastructure as Code (IaC)
Modern approach to IT infrastructure management that automates provisioning and management through code
■ Used in DevOps and with cloud computing
Idempotence
○ Operation consistently produces the same results
○ Crucial for consistency and reliability in multiple environments
Idempotence ensures identical environments. It is the abiity to produce the same results as many times as it is executed
IaC Method
Developers and ops teams manage infrastructure through code
A method in which IT infrastructures are defined in code files that can be versioned, tested and audited
■ High-level languages like YAML, JSON, or domain-specific languages (e.g., HCL)
used
Snowflake Systems
The main goal of IAC is to remove snowflake systems
Snowflake sysmtes: A configuration that lacks consistency that might introuduce risks, so it has to be eliminated
Benefits of IaC
■ Speed and Efficiency (of development and deployment processes)
■ Consistency and Standardisation (environments set up same way)
■ Scalability (Operations)
■ Cost Savings (Manual configuration is not good)
■ Auditability and Compliance
IaC Challanges
Learning Curve
● New skills and mindset required
● Teams learn to write, test, and maintain infrastructure code
IaC Challanges
Complexity
● Infrastructure code can become complex
● Mitigated with modularisation and documentation
IaC Challanges
Security Risks
● Sensitive data exposure in code files
● Insecure configurations may be introduced