Amazon S3 (Simple Storage Service) was the second AWS service ever launched, back in 2006, and it is still the one you will touch in almost every AWS project - for backups, logs, build artifacts, static websites, data lakes, Terraform state files and the images on this very blog. It is object storage - you put files …

Introduction Welcome to another Ansible blog post! Today we'll dive deep into Ansible Handlers. Before we jump straight into the demo, let's lay a solid foundation by understanding the 'what' and 'when' of Ansible Handlers - and especially the when, because that is where almost every handler bug comes from. Table of …

Securing Sensitive Data in Terraform Table of Content Introduction Securing Sensitive Data with Terraform 2.1 Securely managing Terraform variables 2.2 Encrypting Sensitive Data at Rest 2.3 Encrypting Sensitive Data in Transit 2.4 The use of sensitive argument in Terraform to prevent logging of sensitive data …

1. Introduction Security in the cloud is not just an option; it's an imperative. Much like a well-guarded fortress, your cloud infrastructure needs robust, scalable defenses. AWS provides us with a wealth of tools and best practices for this task, but managing them manually can feel like trying to organize an unruly …

Terraform, HashiCorp's infrastructure as code (IaC) tool, is a favorite among developers and system administrators for its simplicity and power in managing and provisioning data center infrastructure. However, as with any technology, there are complexities that arise as we go deeper. One such complexity is loading …

TL;DR Yes. Terraform does not care where the API lives. On-premises it talks to vCenter (vmware/vsphere), Proxmox VE (bpg/proxmox), libvirt/KVM (dmacvicar/libvirt), Canonical MAAS for bare metal (canonical/maas) or a Docker engine (kreuzwerker/docker), and the plan/apply/destroy loop is identical to AWS. The …

Today, we'll unravel a common hurdle that you might encounter while working with Terraform and AWS: Error creating IAM Role. MalformedPolicyDocument: Has prohibited field Resource This error can put a wrinkle in your cloud deployment process, but don't worry. I'm here to guide you through it, step by step. By the end …

TL;DR null in Terraform means "not set". Passing null to a resource argument is the same as omitting the argument; passing it into a string, a count or a for_each is an error. Replace it with coalesce(var.port, 8080) when the fallback is a plain value, with var.name != null ? var.name : …

TL;DR TL;DR Two steps: declare output "instance_id" inside module A, then pass module.ec2_module.instance_id as an argument of module B in the root module. Modules never talk to each other directly; the root module is the wire. That one reference is also the dependency: Terraform creates A first and B second. …

TL;DR TL;DR Inside a module you cannot see resources of a sibling or parent module. The only way out is an output block in the child, read from the caller as module.<module_name>.<output_name>. A reference to a name the child never declared fails at validate time with Unsupported attribute; I show the exact …