# Terraform

Terraform is an infrastructure-as-code tool for building, changing, and versioning infrastructure.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Your Kubernetes Knowledge Is Becoming Cheaper. Your Production Judgment Isn't.

DevFeed: [Your Kubernetes Knowledge Is Becoming Cheaper. Your Production Judgment Isn't.](<https://devfeed.tech/articles/your-kubernetes-knowledge-is-becoming-cheaper-your-production-judgment-isn-t-136242.md>)

Original publisher: [Read original article](<https://blog.devops.dev/your-kubernetes-knowledge-is-becoming-cheaper-your-production-judgment-isnt-cabf2adfc61a?source=rss----33f8b2d9a328---4>)

Author: Arvind Verma

Published: 2026-11-16T13:25:19Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>), [AIOps for Kubernetes](<https://devfeed.tech/topics/aiops-for-kubernetes.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bash](<https://devfeed.tech/tags/bash.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [ci-cd-pipeline](<https://devfeed.tech/tags/ci-cd-pipeline.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [commands](<https://devfeed.tech/tags/commands.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [decision](<https://devfeed.tech/tags/decision.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-engineer](<https://devfeed.tech/tags/devops-engineer.md>), [docker](<https://devfeed.tech/tags/docker.md>), [english](<https://devfeed.tech/tags/english.md>), [git](<https://devfeed.tech/tags/git.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [helm](<https://devfeed.tech/tags/helm.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [production](<https://devfeed.tech/tags/production.md>)

### AI overview

The article argues that AI is making configuration such as Kubernetes YAML, Terraform modules, and CI/CD pipelines cheaper to produce, while production judgment remains central to DevOps. It recommends narrowing investigations with evidence, checking the failure's scope and system layer, and treating dashboards as signals rather than proof of user health. Before restarting, rolling back, draining, scaling, or failing over, assess consequences and blast radius; under uncertainty, seek a safe next test. During incidents, communicate impact, hypothesis, evidence being checked, and next action. It also urges engineers to learn failure modes alongside tool mechanics. These are the article's recommendations, not a comparison of specific AI tools.

### Source excerpt

There was a time when knowing how to write Kubernetes YAML felt like a superpower. You knew Deployments. You knew Services. You knew ConfigMaps. You knew Ingress. You knew how to write a Helm chart without accidentally deleting half the cluster. You learned Terraform. You learned Jenkins. You learned Bash. You learned Prometheus queries. You spent years collecting tools, commands, syntax, and implementation patterns. And then AI showed up. Now you can describe what you want in plain English and get a Terraform module. Ask for a Kubernetes Deployment and you get YAML. Ask for a CI/CD pipeline and you get a pipeline. Ask for a Bash script and you get one. Ask for a PromQL query and, assuming the machines haven't collectively decided to punish humanity that day, you get something reasonably useful. 😄 So here's the uncomfortable question: If AI can increasingly handle implementation, what exactly becomes more valuable for a DevOps engineer? I think the answer is simple. Judgment. Not knowing more commands. Not memorizing more YAML. Not collecting another 47 certifications. Knowing what to do when the obvious answer doesn't work. And production has a beautiful way of ensuring that the obvious answer almost never works. 1 The Shift: From Tool Operator to Decision Maker For years, DevOps careers were heavily associated with tools. Learn AWS. Learn Docker. Learn Kubernetes. Learn Terraform. Learn Jenkins. Learn Ansible. Learn Prometheus. Learn Grafana. Learn Git. Learn Linux. And yes, these skills still matter. The tools aren't suddenly useless because AI can generate configuration for them. But something important is changing. The cost of producing configuration is falling. Consider a simple Kubernetes deployment. Previously, an engineer might spend time writing: apiVersion: apps/v1 kind: Deployment metadata: name: payment-api spec: replicas: 3 selector: matchLabels: app: payment-api template: metadata: labels: app: payment-api spec: containers: - name: payment-api image

## Deploy Amazon S3 Files with Terraform

DevFeed: [Deploy Amazon S3 Files with Terraform](<https://devfeed.tech/articles/deploy-amazon-s3-files-with-terraform-133433.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/deploy-amazon-s3-files-with-terraform/>)

Author: Karthik Akula

Published: 2026-11-13T19:06:41Z

Content type: tutorial

Language: en

Sources: [AWS Storage Blog](<https://devfeed.tech/sources/aws-storage-blog.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [mount](<https://devfeed.tech/topics/mount.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [accessible](<https://devfeed.tech/tags/accessible.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [compute](<https://devfeed.tech/tags/compute.md>), [compute-resources](<https://devfeed.tech/tags/compute-resources.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [files](<https://devfeed.tech/tags/files.md>), [groups](<https://devfeed.tech/tags/groups.md>), [iam](<https://devfeed.tech/tags/iam.md>), [module](<https://devfeed.tech/tags/module.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [mount](<https://devfeed.tech/tags/mount.md>), [nfs](<https://devfeed.tech/tags/nfs.md>), [s3](<https://devfeed.tech/tags/s3.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The Terraform module deploys Amazon S3 Files as an NFS file system backed by an S3 bucket, with mount targets in private subnets across multiple Availability Zones. It restricts NFS traffic to TCP 2049 between designated security groups, applies resource and identity IAM policies, configures synchronization and optional customer managed KMS encryption, and creates CloudWatch alarms and a per-client dashboard. Examples cover EC2, ECS on Fargate, and Lambda; ECS and Lambda use access points, while EC2 needs ClientRootAccess to write at the file system root. Prerequisites include Terraform 1.5.0 or later, AWS provider 6.53.0 or later, a versioned and encrypted bucket, and a VPC with private subnets in at least two zones. The article notes that alarms have no data when no client is mounted, and the first Lambda invocation may time out shortly after deployment; retry after about a minute.

### Source excerpt

Amazon S3 Files makes Amazon S3 buckets accessible as NFS mounts from AWS compute resources. This post walks through a Terraform module that deploys S3 Files end-to-end: multi-AZ mount targets, security groups, IAM policies, encryption, and Amazon CloudWatch monitoring.

## Build a multi-team AI and analytics environment on Amazon SageMaker Unified Studio with Terraform

DevFeed: [Build a multi-team AI and analytics environment on Amazon SageMaker Unified Studio with Terraform](<https://devfeed.tech/articles/build-a-multi-team-ai-and-analytics-environment-on-amazon-sagemaker-unified-studio-with-terraform-129559.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/build-a-multi-team-ai-and-analytics-environment-on-amazon-sagemaker-unified-studio-with-terraform/>)

Author: Harshi Surampalli

Published: 2026-11-11T19:58:49Z

Content type: article

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-sagemaker](<https://devfeed.tech/tags/amazon-sagemaker.md>), [amazon-sagemaker-unified-studio](<https://devfeed.tech/tags/amazon-sagemaker-unified-studio.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [apply](<https://devfeed.tech/tags/apply.md>), [blueprints](<https://devfeed.tech/tags/blueprints.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [data](<https://devfeed.tech/tags/data.md>), [data-analytics](<https://devfeed.tech/tags/data-analytics.md>), [domains](<https://devfeed.tech/tags/domains.md>), [environment](<https://devfeed.tech/tags/environment.md>), [generative](<https://devfeed.tech/tags/generative.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [governance](<https://devfeed.tech/tags/governance.md>), [studio](<https://devfeed.tech/tags/studio.md>), [team](<https://devfeed.tech/tags/team.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The Terraform module provisions a shared, governed Amazon SageMaker Unified Studio domain with team-specific project profiles for analytics, machine learning, and generative AI. It combines AWS and AWS Cloud Control providers, enables selected blueprints, and can create least-privilege service roles or use supplied roles; network settings can default to discovery of the default VPC and subnets. The walkthrough requires Terraform 1.7 or later, AWS credentials with resource-management permissions, and Unified Studio in the target Region; IAM Identity Center is needed only for SSO membership. One apply creates the domain, profiles, and an initial project, while further team projects require additional project module blocks or portal creation. Membership supports SSO users and groups plus same-account IAM users and roles. IAM principals need SageMakerStudioUserIAMConsolePolicy or equivalent, which the module does not attach; cross-account role access may be limited and should be verified for the Region. Costs mainly arise from using Redshift Serverless, EMR Serverless, Bedrock, and S3.

### Source excerpt

Learn how to use the Amazon SageMaker Unified Studio Terraform module to provision a multi-team AI and analytics platform (domains, blueprints, project profiles, and projects) for data analytics, machine learning, and generative AI teams in a single terraform apply, with shared governance and least-privilege security defined entirely as code.

## 7 Terraform State File Mistakes That Leak Your Cloud Secrets

DevFeed: [7 Terraform State File Mistakes That Leak Your Cloud Secrets](<https://devfeed.tech/articles/7-terraform-state-file-mistakes-that-leak-your-cloud-secrets-128872.md>)

Original publisher: [Read original article](<https://blog.devops.dev/7-terraform-state-file-mistakes-that-leak-your-cloud-secrets-329b420b9d51?source=rss----33f8b2d9a328---4>)

Author: Vortex 404

Published: 2026-11-11T06:16:13Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [devops](<https://devfeed.tech/tags/devops.md>), [file](<https://devfeed.tech/tags/file.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [leak](<https://devfeed.tech/tags/leak.md>), [mistakes](<https://devfeed.tech/tags/mistakes.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [state](<https://devfeed.tech/tags/state.md>), [state-management](<https://devfeed.tech/tags/state-management.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [terraform-state](<https://devfeed.tech/tags/terraform-state.md>)

### AI overview

Terraform state and plan files can store sensitive infrastructure values in plaintext, and marking a variable sensitive does not remove its value from state. The excerpt cites HashiCorp documentation and a 2024 penetration test involving a publicly readable S3 bucket, where an exposed credential was traced to an administrator-level AWS key in another account. It introduces seven state-file mistakes, but the provided text only begins the first: assuming "sensitive = true" hides the value from state. The remaining mistakes and recommended fixes are not included in this excerpt.

### Source excerpt

Terraform stores sensitive values in plaintext by default -- and marking a variable "sensitive" doesn't change that. Here's what actually... Continue reading on DevOps.dev "

## Runpod Terraform provider 2.0: migrate from 1.x

DevFeed: [Runpod Terraform provider 2.0: migrate from 1.x](<https://devfeed.tech/articles/runpod-terraform-provider-2-0-migrate-from-1-x-124883.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/runpod-terraform-provider-2-0-migration>)

Author: The Team at Runpod

Published: 2026-11-10T06:10:33Z

Content type: tutorial

Language: en

Sources: [Runpod Blog.](<https://devfeed.tech/sources/runpod-blog.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [argument](<https://devfeed.tech/tags/argument.md>), [auth](<https://devfeed.tech/tags/auth.md>), [backends](<https://devfeed.tech/tags/backends.md>), [base](<https://devfeed.tech/tags/base.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [commit](<https://devfeed.tech/tags/commit.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [plan](<https://devfeed.tech/tags/plan.md>), [pod](<https://devfeed.tech/tags/pod.md>), [rest](<https://devfeed.tech/tags/rest.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [terraform-provider](<https://devfeed.tech/tags/terraform-provider.md>)

### AI overview

Runpod Terraform provider 2.0 is generated from the REST v2 API, giving its attributes documented v2 mappings; version 1.x used REST v1, which Runpod is retiring. The provider manages Pods, Serverless endpoints, templates, volumes, Instant Clusters, and registry credentials through Terraform. It requires Terraform 1.6 or later, and the article recommends supplying the API key through `RUNPOD_API_KEY`. Plans let you review changes before applying billable resources; running Pods bill by the minute, so destroy them when finished or set `desired_state = "EXITED"` to stop them while retaining configuration. Migration is breaking: 2.0.0 has no state upgraders, so resources need configuration edits and state actions. Some 1.x Pods may be replaced because v2 reads omit eight create-time attributes; replacement permanently deletes the Pod and anything not on a network volume. The guide advises reviewing planned replacements and describes leaving Pods on 1.x or adopting them with `ignore_changes` before the first apply.

### Source excerpt

## How Runpod's agent skills and MCP server work together An API tells an agent what it can do, not whether it should. See how skills, a concept graph and live-account tests keep agents right on Runpod. Blog Put Runpod in the same Terraform plan as the rest of your stack. Deploy your first Pod, let an agent write the plan and migrate from 1.x. Terraform lets you describe infrastructure as code, preview the changes and apply them.

## ColdFusion Deployment Secrets Exposed in Terraform State

DevFeed: [ColdFusion Deployment Secrets Exposed in Terraform State](<https://devfeed.tech/articles/coldfusion-deployment-secrets-exposed-in-terraform-state-109722.md>)

Original publisher: [Read original article](<https://blog.devops.dev/coldfusion-deployment-secrets-exposed-in-terraform-state-05b66fe7d049?source=rss----33f8b2d9a328---4>)

Author: Deepak Purohit

Published: 2026-10-30T18:59:34Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [CI/CD secrets management](<https://devfeed.tech/topics/ci-cd-secrets-management.md>), [secret rotation](<https://devfeed.tech/topics/secret-rotation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [coldfusion](<https://devfeed.tech/tags/coldfusion.md>), [coldfusion-development](<https://devfeed.tech/tags/coldfusion-development.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [hire-coldfusion-developer](<https://devfeed.tech/tags/hire-coldfusion-developer.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [state](<https://devfeed.tech/tags/state.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [terraform-state](<https://devfeed.tech/tags/terraform-state.md>)

### AI overview

Terraform stores configured secrets in plaintext state and saved plan files; marking variables or outputs `sensitive` only redacts ordinary CLI display, while `-json` and `-raw` can reveal outputs in plaintext. For ColdFusion, the text identifies datasource and administrator passwords passed through the Admin API as exposure paths. It recommends ephemeral values and supported write-only resource arguments to omit credentials from state and plans, or having an instance fetch them from a secret store at runtime using its identity. Ephemeral values do not persist, so needed credentials must be stored elsewhere; write-only support varies by provider/resource. For existing exposure, rotate credentials before cleaning old copies, then audit state backups, plans, version history and CI logs. As interim protection, use remote state with encryption, access controls and audit logs. Verify Terraform-version and ColdFusion-version specifics, including data-source behavior, which the text says its cited pages do not establish.

### Source excerpt

ColdFusion Deployment Secrets Exposed in Terraform StatePlaintext by Design: Getting ColdFusion Secrets Out of Your Terraform State An auditor asks to see your Terraform state file. Someone opens it, searches for "password," and finds the production ColdFusion datasource credential sitting there in readable text. Alongside it is the ColdFusion administrator password, because a provisioning script needed it. Nobody made a mistake. No misconfiguration caused this. Terraform recorded those values because that is what it does with values you give it, and the documentation says so plainly. The uncomfortable part is what comes next. That state file has been copied into backups. It may have been committed to a repository years ago. Engineers who have since left the company had read access to it. Every one of those copies still contains the credential. This guide explains why secrets land in state, why the setting most teams rely on does not prevent it, and what actually keeps them out. It uses the Terraform and Adobe ColdFusion documentation. Lucid Outsourcing Solutions helps enterprise teams build ColdFusion deployment pipelines where credentials never reach a state file. Why Does Terraform Put Secrets in State at All? Because state is a record of what Terraform did, and credentials are part of what it did. HashiCorp's documentation is direct about this. The sensitive data guidance states that "Terraform state and plan files contain detailed information about your infrastructure." It then gives the specific warning: "Terraform stores your state in a plaintext file, which includes any secret values you defined in your configuration." The examples it names include initial database passwords and API tokens. Note the second artifact in that sentence. Plan files are mentioned alongside state files. A saved plan is another place the same credential lives, which teams often overlook entirely. The page's advice follows from that: treat the state file as sensitive data and keep it

## What is the best agentic infrastructure automation platform to buy for a mid-sized enterprise in the UK?

DevFeed: [What is the best agentic infrastructure automation platform to buy for a mid-sized enterprise in the UK?](<https://devfeed.tech/articles/what-is-the-best-agentic-infrastructure-automation-platform-to-buy-for-a-mid-sized-enterprise-in-the-uk-105585.md>)

Original publisher: [Read original article](<https://www.rogerperkin.co.uk/itential/what-is-the-best-agentic-infrastructure-automation-platform-to-buy-for-a-mid-sized-enterprise-in-the-uk/>)

Author: Roger Perkin

Published: 2026-10-28T08:56:10Z

Content type: opinion

Language: en

Sources: [Roger Perkin Network Automation Consultant](<https://devfeed.tech/sources/roger-perkin-network-automation-consultant.md>)

Topics: [Automation](<https://devfeed.tech/topics/automation.md>), [Ansible](<https://devfeed.tech/topics/ansible.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-infrastructure](<https://devfeed.tech/tags/agentic-infrastructure.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ansible](<https://devfeed.tech/tags/ansible.md>), [automation](<https://devfeed.tech/tags/automation.md>), [best](<https://devfeed.tech/tags/best.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-automation](<https://devfeed.tech/tags/infrastructure-automation.md>), [itential](<https://devfeed.tech/tags/itential.md>), [networks](<https://devfeed.tech/tags/networks.md>), [platform](<https://devfeed.tech/tags/platform.md>), [python](<https://devfeed.tech/tags/python.md>), [recommendation](<https://devfeed.tech/tags/recommendation.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [tools](<https://devfeed.tech/tags/tools.md>), [uk](<https://devfeed.tech/tags/uk.md>)

### AI overview

The source recommends Itential for mid-sized UK enterprises with mixed infrastructure and existing Ansible, Terraform and Python automation. It describes Itential as orchestrating those tools as governed services, which AI agents can call through FlowAI and the Itential MCP Server. Engineers' and agents' actions pass through the same role-based access controls, approval gates and audit trail; agents do not access infrastructure directly. The source says this audit evidence matters for UK GDPR and sector regulation, notes Itential's 2026 recognition in five Gartner Market Guides, and recommends testing shortlisted platforms against two or three real use cases before purchase.

### Source excerpt

For most mid-sized UK enterprises, my recommendation is Itential. Mid-sized teams rarely run a single-vendor estate. You've got multi-vendor networks, some cloud, and a collection of Ansible playbooks, Terraform modules and Python scripts that already work. Itential doesn't ask you to replace any of that. It orchestrates those tools as governed services, then lets AI ...

## CVE-2026-116676 - Atlantis: OS command injection through PR-controlled Terraform workspace enables RCE during plan

DevFeed: [CVE-2026-116676 - Atlantis: OS command injection through PR-controlled Terraform workspace enables RCE during plan](<https://devfeed.tech/articles/cve-2026-116676-atlantis-os-command-injection-through-pr-controlled-terraform-workspace-enables-rce-during-plan-102513.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-116676>)

Author: CVEFEED.io; github.com

Published: 2026-10-27T18:17:35Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Shell](<https://devfeed.tech/topics/shell.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [application](<https://devfeed.tech/tags/application.md>), [apply](<https://devfeed.tech/tags/apply.md>), [atlantis](<https://devfeed.tech/tags/atlantis.md>), [command-injection](<https://devfeed.tech/tags/command-injection.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-116676](<https://devfeed.tech/tags/cve-2026-116676.md>), [os](<https://devfeed.tech/tags/os.md>), [plan](<https://devfeed.tech/tags/plan.md>), [pr](<https://devfeed.tech/tags/pr.md>), [published](<https://devfeed.tech/tags/published.md>), [rce](<https://devfeed.tech/tags/rce.md>), [runatlantis](<https://devfeed.tech/tags/runatlantis.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

CVE-2026-116676 affects Atlantis versions 0.4.0 through versions before 0.47.1: during a plan, Atlantis joins Terraform arguments containing a pull-request-controlled workspace with spaces and executes them through `sh -c`. An authenticated contributor whose pull request is eligible for a plan can use shell metacharacters in the workspace name to run commands as the Atlantis service account, without apply permission, custom workflows, or a malicious provider. Fork pull requests are exposed only when `--allow-fork-prs` is enabled; eligible same-repository branches do not require it. Executed commands inherit the service environment and may access credentials, files, state, and network resources available to Atlantis. The issue is fixed in 0.47.1.

### Source excerpt

CVE ID :CVE-2026-116676 Published : Oct. 27, 2026, 6:17 p.m. | 1 hour, 26 minutes ago Description :Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. From version 0.4.0 until 0.47.1, Atlantis passes the pull-request-controlled workspace value from atlantis.yaml into Terraform command arguments that are joined with strings.Join(args, " ") and executed through sh -c. An authenticated contributor whose pull request is eligible for an Atlantis plan can include shell metacharacters in the workspace name, causing arbitrary commands to execute as the Atlantis service account without custom workflows, apply permission, or a malicious Terraform provider. External contributors can reach the flaw through fork pull requests only when --allow-fork-prs is enabled, while eligible same-repository branches do not require that option. The commands inherit the Atlantis process environment and can access cloud-provider, Terraform, and version-control credentials as well as files, state, and network resources available to the service. This issue is fixed in version 0.47.1. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Do AI Coding Agents Write Infrastructure as Code Like Humans? An Empirical Study of GitHub Pull Requests

DevFeed: [Do AI Coding Agents Write Infrastructure as Code Like Humans? An Empirical Study of GitHub Pull Requests](<https://devfeed.tech/articles/do-ai-coding-agents-write-infrastructure-as-code-like-humans-an-empirical-study-of-github-pull-requests-101780.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.34613>)

Author: Amine Barrak, Emna Ksontini, Charles Wehbe

Published: 2026-10-27T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [coding assistant](<https://devfeed.tech/topics/coding-assistant.md>)

Tags: [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [github](<https://devfeed.tech/tags/github.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [study](<https://devfeed.tech/tags/study.md>), [sustainability](<https://devfeed.tech/tags/sustainability.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

Across 349,156 IaC pull requests from 49,241 GitHub repositories, agent contributions were about four times larger than human PRs and more often changed core infrastructure; automation bots mainly maintained dependencies. Silent-agent PRs had a higher overall merge rate than human PRs (87.4% vs. 78.9%), but a 4.0-point lower rate within the same repositories. Disclosed agents created new infrastructure more often (34.0% vs. 21.4%) and were 8.4 points less likely to have PRs merged for the same change type within a repository; silent agents had comparable acceptance for most change types. In 2,645 matched Terraform PR pairs, agent and human PRs showed similar rates of sustainability smells (10.4% vs. 10.3%; paired odds ratio 1.02, 95% CI 0.83-1.25), commonly missing remote state and monolithic configurations. The study also found agent traces in 12.3% of PRs remaining after bot identification, with that share increasing over time.

### Source excerpt

arXiv:2610.34613v1 Announce Type: new Abstract: Infrastructure-as-Code (IaC) configurations define cloud resources, networking, and access control, and AI coding agents increasingly write them. Little is known about how agent contributions differ from those of humans and automation bots, how maintainers evaluate them, and whether they introduce different sustainability concerns. We study 349,156 IaC pull requests (PRs) from 49,241 GitHub repositories, distinguishing humans, automation bots, silent agents, and disclosed agents. Bots account for 32.9% of ostensibly human PRs, and 12.3% of the remaining PRs contain agent traces, a share that grows over the study period. Agent PRs are about four times larger than human PRs and more often modify core infrastructure modules, whereas bots mainly maintain dependencies. Silent-agent PRs have higher overall merge rates than human PRs (87.4% vs. 78.9%) but are merged 4.0 percentage points less often within the same repositories. Disclosed agents create new infrastructure more often than humans (34.0% vs. 21.4%), and even for the same change type within the same repository, their PRs are 8.4 points less likely to be merged; silent-agent PRs show comparable acceptance for most change types. Finally, in 2,645 matched agent-human Terraform PR pairs, agent and human PRs introduce sustainability smells at similar rates (10.4% vs. 10.3%; paired odds ratio 1.02, 95% CI 0.83-1.25), most commonly missing remote state and monolithic configurations.

## Tracing failures across Terraform state boundaries with AWS DevOps Agent

DevFeed: [Tracing failures across Terraform state boundaries with AWS DevOps Agent](<https://devfeed.tech/articles/tracing-failures-across-terraform-state-boundaries-with-aws-devops-agent-101178.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/tracing-failures-across-terraform-state-boundaries-with-aws-devops-agent/>)

Author: Shruti Saxena

Published: 2026-10-26T17:21:23Z

Content type: article

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [DevOps](<https://devfeed.tech/topics/devops.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [application](<https://devfeed.tech/tags/application.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cause](<https://devfeed.tech/tags/cause.md>), [change](<https://devfeed.tech/tags/change.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [generate](<https://devfeed.tech/tags/generate.md>), [kiro](<https://devfeed.tech/tags/kiro.md>), [post](<https://devfeed.tech/tags/post.md>), [root](<https://devfeed.tech/tags/root.md>), [shows](<https://devfeed.tech/tags/shows.md>), [stack](<https://devfeed.tech/tags/stack.md>), [state](<https://devfeed.tech/tags/state.md>), [team](<https://devfeed.tech/tags/team.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [this](<https://devfeed.tech/tags/this.md>), [traces](<https://devfeed.tech/tags/traces.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The demo shows how AWS DevOps Agent can trace an application outage across independent Terraform states: a tightened security group egress rule blocks Lambda's TCP/443 path through a DynamoDB Gateway VPC endpoint, causing timeouts and misleading alarms. The agent correlates the alarms, resource dependencies, logs, metrics, and CloudTrail change; it reasons about AWS resources rather than identifying Terraform stack ownership. VPC Flow Logs provide additional evidence, and without them the network diagnosis has less support. The agent produces a mitigation specification; Kiro uses it to generate a Terraform fix for engineer review, planning, and application. The article notes that CloudTrail attributes Terraform changes to the IAM role that ran apply, not necessarily the individual engineer. Its sample intentionally injects failure and exposes an unauthenticated API, so it is not production-ready.

### Source excerpt

When a change in one Terraform stack silently breaks an application in another, the team seeing the symptoms often doesn't own the stack that caused it. This post shows how AWS DevOps Agent traces the root cause across Terraform state boundaries, then pairs with Kiro to generate the fix.

## CVE-2026-102649 - Burrito: Unauthenticated webhooks trigger unauthorized Terraform plans when webhookSecret is unset

DevFeed: [CVE-2026-102649 - Burrito: Unauthenticated webhooks trigger unauthorized Terraform plans when webhookSecret is unset](<https://devfeed.tech/articles/cve-2026-102649-burrito-unauthenticated-webhooks-trigger-unauthorized-terraform-plans-when-webhooksecret-is-unset-100644.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-102649>)

Author: CVEFEED.io

Published: 2026-10-26T17:09:08Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-102649](<https://devfeed.tech/tags/cve-2026-102649.md>), [github](<https://devfeed.tech/tags/github.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-operator](<https://devfeed.tech/tags/kubernetes-operator.md>), [plan](<https://devfeed.tech/tags/plan.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [repository](<https://devfeed.tech/tags/repository.md>), [secret](<https://devfeed.tech/tags/secret.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [webhooks](<https://devfeed.tech/tags/webhooks.md>)

### AI overview

Before 0.13.0, Burrito accepts unsigned GitHub and GitLab webhook events if a TerraformRepository credential has no webhookSecret or an empty one. Someone who can reach the webhook endpoint and knows a tracked repository URL can forge events that create or delete TerraformPullRequest resources. A forged GitHub event pairing a real pull request number with another existing branch can trigger an unauthorized terraform plan using stored git and cloud credentials; the plan may also be posted to the real pull request, exposing and misattributing infrastructure changes. Auto-apply is disabled for these temporary layers, so the flaw alone cannot force terraform apply. Plan-time provider or data-source execution depends on the selected branch's contents. The issue is fixed in version 0.13.0.

### Source excerpt

CVE ID :CVE-2026-102649 Published : Oct. 26, 2026, 5:09 p.m. | 1 hour, 3 minutes ago Description :Burrito is a Terraform Automation Collaboration Software (TACoS) Kubernetes operator. Prior to 0.13.0, `POST /api/webhook` accepts unsigned GitHub and GitLab events when a `TerraformRepository`'s credentials omit `webhookSecret` or set it to an empty value, including credentials configured for git authentication and polling. `Credential.WebhookSecret` is optional, and `go-playground/webhooks` skips signature or token verification when the secret is empty. Anyone who can reach `burrito-server`'s endpoint and knows a tracked repository's URL can forge events to create or delete `TerraformPullRequest` custom resources with attacker-chosen `Branch`, `Base`, and `ID` fields. For GitHub `pull_request` events, the controller fetches changed files using the real pull request number but does not cross-check the payload's branch against that pull request. Pairing a real, existing pull request number with an unrelated existing branch in the same repository can therefore cause an unauthorized `terraform plan` for affected layers using the operator's stored git and cloud credentials. Code analysis also indicates that the resulting plan can be posted to the real pull request's comment thread, exposing and misattributing another branch's infrastructure changes. Auto-apply is disabled for these temporary layers, so this vulnerability alone cannot force a `terraform apply`; plan-time provider and data-source code execution depends on the selected branch's contents. This issue is fixed in version 0.13.0. Severity: 9.9 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Can AI Govern the Infrastructure Code It Writes?

DevFeed: [Can AI Govern the Infrastructure Code It Writes?](<https://devfeed.tech/articles/can-ai-govern-the-infrastructure-code-it-writes-103467.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/ai-infrastructure-code-governance>)

Author: Mrinalini Sugosh

Published: 2026-10-23T00:00:00Z

Content type: article

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [platform engineering automation](<https://devfeed.tech/topics/platform-engineering-automation.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [opentofu](<https://devfeed.tech/topics/opentofu.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [alert](<https://devfeed.tech/tags/alert.md>), [all](<https://devfeed.tech/tags/all.md>), [allows](<https://devfeed.tech/tags/allows.md>), [ansible](<https://devfeed.tech/tags/ansible.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [builds](<https://devfeed.tech/tags/builds.md>), [can](<https://devfeed.tech/tags/can.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [learn](<https://devfeed.tech/tags/learn.md>), [outages](<https://devfeed.tech/tags/outages.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [trace](<https://devfeed.tech/tags/trace.md>)

### AI overview

The text argues that AI can speed up writing Terraform while leaving operations as the bottleneck: it cites platform teams spending up to 40% of their time maintaining and troubleshooting infrastructure code, and says more than 70% of outages stem from drift or manual changes. It presents Terraform, OpenTofu, and CDK as infrastructure builders, Terragrunt as an organizer for scale, and Ansible as a Day 2 configuration tool. A proposed unified control plane would let teams define approved patterns for developers and AI agents without replacing those tools. The described Remediation Agent detects drift and opens a pull request with a proposed fix; the Blast Radius Agent assesses dependent-system risk before deployment. These are presented as ways to govern AI-generated changes to the same operational standard as human-authored ones.

### Source excerpt

AI writes Terraform in seconds, but 70% of infrastructure outages trace to drift or manual changes. Learn to govern and heal what AI builds. | Blog

## Infrastructure Migrations: Your complete AWS re:Invent 2026 guide

DevFeed: [Infrastructure Migrations: Your complete AWS re:Invent 2026 guide](<https://devfeed.tech/articles/infrastructure-migrations-your-complete-aws-re-invent-2026-guide-95807.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/migration-and-modernization/infrastructure-migrations-your-complete-aws-reinvent-2026-guide/>)

Author: Suhail Fouzan

Published: 2026-10-22T14:42:33Z

Content type: article

Language: en

Sources: [Migration & Modernization](<https://devfeed.tech/sources/migration-modernization.md>)

Topics: [AWS Transform](<https://devfeed.tech/topics/aws-transform.md>), [AWS Outposts](<https://devfeed.tech/topics/aws-outposts.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [data centers](<https://devfeed.tech/topics/data-centers.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-vmware-service-amazon-evs](<https://devfeed.tech/tags/amazon-elastic-vmware-service-amazon-evs.md>), [amazon-fsx-for-netapp-ontap](<https://devfeed.tech/tags/amazon-fsx-for-netapp-ontap.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [automate](<https://devfeed.tech/tags/automate.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-re-invent](<https://devfeed.tech/tags/aws-re-invent.md>), [aws-transform](<https://devfeed.tech/tags/aws-transform.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [migration](<https://devfeed.tech/tags/migration.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [server](<https://devfeed.tech/tags/server.md>), [workshops](<https://devfeed.tech/tags/workshops.md>)

### AI overview

The guide presents AWS Transform as an agentic AI service for automating migration work from discovery and wave planning through network conversion, cutover, and later modernization. It describes hands-on workflows for rehosting servers to EC2, containerizing applications to ECS or EKS, and generating landing zones and network configurations as infrastructure as code. Customer examples include Fanatics' migration of 1,800 servers across five data centers with projected 48% infrastructure savings, and HealthEdge's ongoing plan to move 8,700 servers and 1,600 databases while serving health plans without business disruption. For organizations keeping VMware, Amazon EVS runs VMware Cloud Foundation in an Amazon VPC on EC2 bare metal, preserving existing tools and processes; Outposts supports workloads that must remain on premises for residency, sovereignty, or latency needs. The guide also covers post-migration stabilization, observability, rightsizing, and security practices. It is a session guide, and schedules may change; the official event catalog is identified as the source for current details.

### Source excerpt

Moving off on-premises infrastructure used to mean months of discovery spreadsheets, dependency mapping workshops, and hand-built wave plans before a single server moved. At AWS re:Invent 2026, running November 30 to December 4 in Las Vegas, you can see how agentic AI is changing that. AWS Transform uses purpose-built AI agents to automate the migration [...]

## Terraform Just Got Its Own Native Policy-as-Code Framework. Sentinel and OPA Are No Longer Required

DevFeed: [Terraform Just Got Its Own Native Policy-as-Code Framework. Sentinel and OPA Are No Longer Required](<https://devfeed.tech/articles/terraform-just-got-its-own-native-policy-as-code-framework-sentinel-and-opa-are-no-longer-required-95221.md>)

Original publisher: [Read original article](<https://blog.devops.dev/terraform-just-got-its-own-native-policy-as-code-framework-sentinel-and-opa-are-no-longer-required-04a60fc1c989?source=rss----33f8b2d9a328---4>)

Author: Vortex 404

Published: 2026-10-22T08:54:18Z

Content type: news

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [policy-as-code](<https://devfeed.tech/topics/policy-as-code.md>), [Open Policy Agent](<https://devfeed.tech/topics/open-policy-agent.md>)

Tags: [apply](<https://devfeed.tech/tags/apply.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [devops](<https://devfeed.tech/tags/devops.md>), [framework](<https://devfeed.tech/tags/framework.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [hashicorp](<https://devfeed.tech/tags/hashicorp.md>), [hcl](<https://devfeed.tech/tags/hcl.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [native](<https://devfeed.tech/tags/native.md>), [opa](<https://devfeed.tech/tags/opa.md>), [plan](<https://devfeed.tech/tags/plan.md>), [policies](<https://devfeed.tech/tags/policies.md>), [policy](<https://devfeed.tech/tags/policy.md>), [policy-as-code](<https://devfeed.tech/tags/policy-as-code.md>), [policy-enforcement](<https://devfeed.tech/tags/policy-enforcement.md>), [query](<https://devfeed.tech/tags/query.md>), [rego](<https://devfeed.tech/tags/rego.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [terraform-provider](<https://devfeed.tech/tags/terraform-provider.md>)

### AI overview

Terraform 1.17.0-rc2 made Terraform Policy (`tfpolicy`) generally available as a built-in, HCL-based policy framework. The excerpt says its `-policies` flag can be used with `plan`, `apply`, and `query` without an experimental build or flag. It contrasts this with Sentinel and OPA as separate policy layers using their own languages, while noting both remain supported. The excerpt begins to describe `tfpolicy` as built on Terraform and its provider ecosystem, but cuts off before explaining further differences or capabilities.

### Source excerpt

Terraform Policy reached GA in 1.17.0-rc2 -- written in the same HCL you already use, and able to check live infrastructure, not just the... Continue reading on DevOps.dev "

## Introducing Terraform Auth0 Modules

DevFeed: [Introducing Terraform Auth0 Modules](<https://devfeed.tech/articles/introducing-terraform-auth0-modules-95927.md>)

Original publisher: [Read original article](<https://auth0.com/blog/terraform-auth0-modules/>)

Author: Rajat Bajaj

Published: 2026-10-22T00:00:00Z

Content type: tutorial

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [account](<https://devfeed.tech/tags/account.md>), [acme](<https://devfeed.tech/tags/acme.md>), [actions](<https://devfeed.tech/tags/actions.md>), [addition](<https://devfeed.tech/tags/addition.md>), [apis](<https://devfeed.tech/tags/apis.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [custom](<https://devfeed.tech/tags/custom.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [mfa](<https://devfeed.tech/tags/mfa.md>), [module](<https://devfeed.tech/tags/module.md>), [modules](<https://devfeed.tech/tags/modules.md>), [roles](<https://devfeed.tech/tags/roles.md>), [set](<https://devfeed.tech/tags/set.md>), [sso](<https://devfeed.tech/tags/sso.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [up](<https://devfeed.tech/tags/up.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Terraform Auth0 Modules package a reusable B2B identity setup into the `b2b-saas-starter` module, built on the Auth0 Terraform Provider. One module block can create an application and RBAC-protected API, plus tenant-wide MFA and attack protection settings. Defaults include RBAC permissions in access tokens, PKCE and rotating refresh tokens, brute-force and breached-password protections, and TOTP MFA; inputs can override them. The module also accepts roles and permissions as data, validates undeclared role references during `terraform plan`, and can configure organization-specific SAML or OIDC SSO. Custom domains require DNS verification after the DNS record is live, typically across two applies; Terraform-managed DNS can allow one apply. Use Terraform 1.3 or later, an Auth0 tenant, and a Management API-authorized M2M application. Because tenant settings, MFA, and attack protection are shared, only one module instance should manage them; additional app instances can disable those management inputs.

### Source excerpt

Set up apps, APIs, roles, MFA, enterprise SSO, and custom domains on Auth0 with a single Terraform module.

## The Multi-Cluster Terraform Survival Guide: Managing Multiple Kubernetes & EKS Environments in a...

DevFeed: [The Multi-Cluster Terraform Survival Guide: Managing Multiple Kubernetes & EKS Environments in a...](<https://devfeed.tech/articles/the-multi-cluster-terraform-survival-guide-managing-multiple-kubernetes-eks-environments-in-a-90787.md>)

Original publisher: [Read original article](<https://blog.devops.dev/the-multi-cluster-terraform-survival-guide-managing-multiple-kubernetes-eks-environments-in-a-8626c394be16?source=rss----33f8b2d9a328---4>)

Author: Techie Crow

Published: 2026-10-20T13:25:50Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>)

Tags: [aliases](<https://devfeed.tech/tags/aliases.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [database](<https://devfeed.tech/tags/database.md>), [devops](<https://devfeed.tech/tags/devops.md>), [eks](<https://devfeed.tech/tags/eks.md>), [environments](<https://devfeed.tech/tags/environments.md>), [ephemeral](<https://devfeed.tech/tags/ephemeral.md>), [fetching](<https://devfeed.tech/tags/fetching.md>), [ingress](<https://devfeed.tech/tags/ingress.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [logging](<https://devfeed.tech/tags/logging.md>), [mappings](<https://devfeed.tech/tags/mappings.md>), [modules](<https://devfeed.tech/tags/modules.md>), [multi-region](<https://devfeed.tech/tags/multi-region.md>), [multiple](<https://devfeed.tech/tags/multiple.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [providers](<https://devfeed.tech/tags/providers.md>), [root](<https://devfeed.tech/tags/root.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

The introduction frames a Terraform pipeline targeting multiple Kubernetes and EKS clusters across regions, environments, AWS accounts, and Kubernetes versions. It says a single default provider does not cover that setup, while separate workspaces or copied configurations risk code drift and maintenance problems. The guide proposes coordinating clusters in one apply with provider aliases, dynamic token fetching, and module mappings, including when the Terraform runner itself runs in a Kubernetes pod. The supplied text does not show the architecture details or implementation steps.

### Source excerpt

Introduction Continue reading on DevOps.dev "

## Configuring Terraform IaC pipelines to provision cloud resources in Cloud and Kubernetes...

DevFeed: [Configuring Terraform IaC pipelines to provision cloud resources in Cloud and Kubernetes...](<https://devfeed.tech/articles/configuring-terraform-iac-pipelines-to-provision-cloud-resources-in-cloud-and-kubernetes-90782.md>)

Original publisher: [Read original article](<https://blog.devops.dev/configuring-terraform-iac-pipelines-to-provision-cloud-resources-in-cloud-and-kubernetes-3ff863fe983e?source=rss----33f8b2d9a328---4>)

Author: Oleh Adam Dubnytskyy

Published: 2026-10-20T13:25:47Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [CI/CD secrets management](<https://devfeed.tech/topics/ci-cd-secrets-management.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [aws-sts](<https://devfeed.tech/tags/aws-sts.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [eks](<https://devfeed.tech/tags/eks.md>), [environments](<https://devfeed.tech/tags/environments.md>), [github](<https://devfeed.tech/tags/github.md>), [iac](<https://devfeed.tech/tags/iac.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [resources](<https://devfeed.tech/tags/resources.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

The example uses GitHub Actions OIDC federation to obtain temporary AWS credentials for Terraform without storing long-lived AWS keys in GitHub. It provisions an IAM OIDC provider and a role whose trust policy restricts the audience and accepted repository refs, then grants that role AWS permissions for services including EKS, S3, DynamoDB, KMS, IAM, and Secrets Manager. For Kubernetes access, it creates an EKS access entry and shows associating cluster administrator access, with AmazonEKSAdminPolicy or namespace-scoped access as narrower alternatives. The workflow runs Terraform formatting, validation, linting, and planning on pull requests, then applies after merge to main. The author calls this a starting point and recommends separate plan/apply roles, an approval gate, isolated self-hosted runners, and least-privilege Kubernetes access; a GitOps setup with ArgoCD or FluxCD can remove the pipeline's need for cluster access.

### Source excerpt

Configuring Terraform IaC pipelines to provision cloud resources in Cloud and Kubernetes environments How do you build a GitHub Actions workflow that provisions cloud resources securely, without storing long-lived credentials? In this post I'll walk through my setup: GitHub Actions for CI, AWS (including Amazon EKS) as the cloud platform, and Terraform as the IaC tool. Security Secure interaction between CI and Cloud platform practice can be adapted with Open ID Connect in Amazon Web Services. OpenID Connect (OIDC) allows your GitHub Actions workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived GitHub secrets. OIDC federation lets external workloads exchange a token from a trusted identity provider for temporary AWS credentials. Here, GitHub signs a short-lived JWT for each job, AWS STS validates it against the IAM OIDC provider and the role's trust policy, and returns credentials that expire automatically, so no AWS keys are stored in GitHub. AWS docs Follow the principle of least privilege for CI/CD. Think twice before granting broad permissions to IaC pipelines that assume roles via OIDC. Step 1. Provision GitHub OIDC provider to IAM # OIDC resource "aws_iam_openid_connect_provider" "github_actions" { url = "https://token.actions.githubusercontent.com" client_id_list = ["sts.amazonaws.com"] } Step 2. Provision IAM role -- github-actions-iac-pipeline to provision cloud resources in cloud platform. Trusted Entity The trust policy defines which principals can assume the role, and under which conditions. A trust policy is a specific type of resource-based policy for IAM roles. { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Federated": "arn:aws:iam::aws-account-id:oidc-provider/token.actions.githubusercontent.com" }, "Action": "sts:AssumeRoleWithWebIdentity", "Condition": { "StringEquals": { "token.actions.githubusercontent.com:aud": "sts.amazonaws.com" }, "StringLike": { "

## PostgreSQL Infrastructure as Code: Consistent Deployment and Operations

DevFeed: [PostgreSQL Infrastructure as Code: Consistent Deployment and Operations](<https://devfeed.tech/articles/postgresql-infrastructure-as-code-consistent-deployment-and-operations-88442.md>)

Original publisher: [Read original article](<https://severalnines.com/blog/postgresql-infrastructure-as-code-consistent-deployment-and-operations/>)

Author: Jessie Baynas

Published: 2026-10-16T06:00:00Z

Content type: tutorial

Language: en

Sources: [SeveralNines](<https://devfeed.tech/sources/severalnines.md>)

Topics: [iac-security](<https://devfeed.tech/topics/iac-security.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>)

Tags: [ansible](<https://devfeed.tech/tags/ansible.md>), [configuration-management](<https://devfeed.tech/tags/configuration-management.md>), [database-automation](<https://devfeed.tech/tags/database-automation.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [deployment-scaling](<https://devfeed.tech/tags/deployment-scaling.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [operations](<https://devfeed.tech/tags/operations.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [puppet](<https://devfeed.tech/tags/puppet.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

This tutorial explains how infrastructure as code can make PostgreSQL environments more consistent through versioned provisioning and configuration. It distinguishes infrastructure management from persistent data and schema migrations, describes how Terraform, Ansible, Puppet, Helm, and Chef can fit into a toolchain, and shows ways to automate PostgreSQL operations with ClusterControl. It also covers testing schema migrations in CI and keeping database tasks from being managed by conflicting systems.

### Source excerpt

Every team running PostgreSQL eventually runs into the same problem: someone tunes a database by hand on a Tuesday afternoon, and six months later nobody can reproduce it. A new environment gets spun up "close enough" to production, a config setting drifts, a role never gets created, and a five minute incident turns into a [...] The post PostgreSQL Infrastructure as Code: Consistent Deployment and Operations appeared first on Severalnines.

## Buildkite updates MCP tools, GitHub Actions support, and CI caching

DevFeed: [Buildkite updates MCP tools, GitHub Actions support, and CI caching](<https://devfeed.tech/articles/shipped-this-week-84286.md>)

Original publisher: [Read original article](<https://buildkite.com/resources/blog/shipped-this-week-october-2-9-2026/>)

Author: Matt Mejia

Published: 2026-10-09T19:51:26Z

Content type: news

Language: en

Sources: [Buildkite](<https://devfeed.tech/sources/buildkite.md>)

Topics: [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [test-engine](<https://devfeed.tech/tags/test-engine.md>)

### AI overview

From October 2 to 9, 2026, Buildkite released MCP tools that prioritize blocking build failures and retry infrastructure failures, expanded GitHub Actions compatibility, and added API reporting for billable active-user usage. Other updates include Terraform support for managing organization membership and roles, custom AWS OIDC audiences, and agent features for reusing cached commands and Git LFS objects.

### Source excerpt

Buildkite shipped MCP server tools that put blocking failures first and retry only infrastructure failures, closer GitHub Actions compatibility, and billable active-user usage in the Buildkite API between October 2 and October 9, 2026. Platform teams can now manage organization memberships in Terraform, give each AWS role its own OpenID Connect (OIDC) audience, and move the Elastic CI Stack for AWS Terraform module to agent v4. Agent v4.2.1 and v4.3.0 also skip cached commands and cache Git Large File Storage (LFS) objects, and the Tests plugin v1.1.0 adds manual test selection.

## HashiCorp Releases Terraform Google Cloud Provider 8.0

DevFeed: [HashiCorp Releases Terraform Google Cloud Provider 8.0](<https://devfeed.tech/articles/hashicorp-relased-terraform-google-cloud-provider-8-0-in-general-availability-83969.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/terraform-google-cloud-provider/>)

Author: Claudio Masolo

Published: 2026-10-09T08:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>)

Tags: [devops](<https://devfeed.tech/tags/devops.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [hashicorp](<https://devfeed.tech/tags/hashicorp.md>), [load-balancing](<https://devfeed.tech/tags/load-balancing.md>), [news](<https://devfeed.tech/tags/news.md>), [release](<https://devfeed.tech/tags/release.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [terraform-google-cloud-provider](<https://devfeed.tech/tags/terraform-google-cloud-provider.md>)

### AI overview

HashiCorp has released version 8.0 of its Terraform provider for Google Cloud. The breaking update changes the default load-balancing scheme for two Compute Engine resources, removes resources tied to retired services, and converts some order-insensitive attributes from lists to sets. Teams should review configuration and plans before upgrading.

### Source excerpt

HashiCorp has announced the general availability of version 8.0 of the Terraform provider for Google Cloud. The major release updates the default load balancing for two Compute Engine resources. It also removes resources linked to retired Google Cloud services. By Claudio Masolo

## Implementing customer managed keys for AWS Lambda durable functions with Terraform

DevFeed: [Implementing customer managed keys for AWS Lambda durable functions with Terraform](<https://devfeed.tech/articles/implementing-customer-managed-keys-for-aws-lambda-durable-functions-with-terraform-62110.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/implementing-customer-managed-keys-for-aws-lambda-durable-functions-with-terraform/>)

Author: Rajdeep Banerjee

Published: 2026-09-29T17:14:00Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [aws-key-management-service](<https://devfeed.tech/tags/aws-key-management-service.md>), [aws-kms](<https://devfeed.tech/tags/aws-kms.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [checkpoint](<https://devfeed.tech/tags/checkpoint.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [least-privilege](<https://devfeed.tech/tags/least-privilege.md>), [payment](<https://devfeed.tech/tags/payment.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

The post explains how to encrypt AWS Lambda durable execution data with a customer managed AWS KMS key. It covers key policies that limit permissions, key rotation and deletion considerations, CloudTrail verification, and deployment with Terraform for regulated payment processing workloads.

### Source excerpt

Lambda durable functions checkpoint execution state to durable storage, and for regulated payment workloads that data is sensitive. This post shows how to configure a customer managed key in AWS KMS to encrypt durable execution data, define a least-privilege key policy, and verify encryption through AWS CloudTrail, all deployed with Terraform.

## Automating Amazon Textract adapter lifecycle management across accounts

DevFeed: [Automating Amazon Textract adapter lifecycle management across accounts](<https://devfeed.tech/articles/automating-amazon-textract-adapter-lifecycle-management-across-accounts-61386.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/automating-amazon-textract-adapter-lifecycle-management-across-accounts/>)

Author: Bhavya Sruthi Sode

Published: 2026-09-28T15:49:04Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Textract](<https://devfeed.tech/topics/amazon-textract.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [adapter pattern](<https://devfeed.tech/topics/adapter-pattern.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>)

Tags: [amazon-textract](<https://devfeed.tech/tags/amazon-textract.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [cloudformation](<https://devfeed.tech/tags/cloudformation.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [iam](<https://devfeed.tech/tags/iam.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [least-privilege](<https://devfeed.tech/tags/least-privilege.md>), [security](<https://devfeed.tech/tags/security.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

This tutorial describes production lifecycle management for Amazon Textract adapters across AWS accounts. It covers infrastructure templates, cross-account promotion, adapter ID management through Systems Manager Parameter Store, pre-classification routing, and security configurations. The described process aims to update production adapter references without application redeployment.

### Source excerpt

Learn how to operationalize Amazon Textract Custom Queries adapters for production: infrastructure as code with AWS CloudFormation and Terraform, a cross-account adapter promotion process, a pre-classification routing pattern for multiple form versions, and production security controls such as VPC endpoints, encryption, and least-privilege IAM.

## Why Terraform Workflows Break Down Across Multiple Teams

DevFeed: [Why Terraform Workflows Break Down Across Multiple Teams](<https://devfeed.tech/articles/why-terraform-workflows-break-down-across-multiple-teams-60710.md>)

Original publisher: [Read original article](<https://hackernoon.com/why-terraform-workflows-break-down-across-multiple-teams?source=rss>)

Author: Mariusz Michalowski

Published: 2026-09-27T19:00:00Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [policy-as-code](<https://devfeed.tech/topics/policy-as-code.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [devops](<https://devfeed.tech/tags/devops.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [terraform-at-scale](<https://devfeed.tech/tags/terraform-at-scale.md>), [terraform-governance](<https://devfeed.tech/tags/terraform-governance.md>), [terraform-workflows](<https://devfeed.tech/tags/terraform-workflows.md>)

### AI overview

The article explains how Terraform workflows become inconsistent across teams when each group maintains separate pipelines, credentials, state backends, policy checks, and infrastructure visibility. It recommends centralizing shared ownership across state and credentials, execution, policy, and drift detection, with approaches including remote state, OIDC, reusable CI workflows, policy as code, and scheduled reconciliation.

### Source excerpt

How to centralize Terraform across multiple teams. Shared state and OIDC federation, one execution model, policy as code, and drift detection you can schedule.

## Configuring Route 53 Subdomain Delegation With Terraform

DevFeed: [Configuring Route 53 Subdomain Delegation With Terraform](<https://devfeed.tech/articles/configuring-route-53-subdomain-delegation-with-terraform-60405.md>)

Original publisher: [Read original article](<https://hackernoon.com/configuring-route-53-subdomain-delegation-with-terraform?source=rss>)

Author: Lucas Tonelli

Published: 2026-09-26T11:00:19Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [DNS](<https://devfeed.tech/topics/dns.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [Infrastructure as code](<https://devfeed.tech/topics/infrastructure-as-code.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Provisioning](<https://devfeed.tech/topics/provisioning.md>)

Tags: [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dns-delegation](<https://devfeed.tech/tags/dns-delegation.md>), [dns-troubleshooting](<https://devfeed.tech/tags/dns-troubleshooting.md>), [environments](<https://devfeed.tech/tags/environments.md>), [history](<https://devfeed.tech/tags/history.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [locking](<https://devfeed.tech/tags/locking.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [public-hosted-zones](<https://devfeed.tech/tags/public-hosted-zones.md>), [route53](<https://devfeed.tech/tags/route53.md>), [subdomain-management](<https://devfeed.tech/tags/subdomain-management.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [terraform-aws-provider](<https://devfeed.tech/tags/terraform-aws-provider.md>), [ttl](<https://devfeed.tech/tags/ttl.md>), [verification](<https://devfeed.tech/tags/verification.md>), [web-hosting](<https://devfeed.tech/tags/web-hosting.md>)

### AI overview

A tutorial on delegating environment subdomains to separate Amazon Route 53 hosted zones with Terraform. It explains how parent and child zones use NS records, and how separation limits DNS blast radius, scopes IAM and CI access, isolates infrastructure-as-code state, and supports verification.

### Source excerpt

Delegate environment subdomains to separate Route 53 hosted zones with Terraform, scoped permissions, and DNS verification checks.

[Next page](<https://devfeed.tech/topics/terraform.md?cursor=WyIyMDI2LTA5LTI2VDExOjAwOjE5KzAwOjAwIiwgImUzYmVlYjFjLWEwY2QtNGI4ZC05ZGU0LTI1OTc4NGI3OGJmMiJd>)