# terraform Published articles for terraform. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases DevFeed: [Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases]() Original publisher: [Read original article]() Author: Sucahyo Ardy Prasetiyo Published: 2026-09-16T08:57:10Z Content type: tutorial Language: en Sources: [SeveralNines]() Topics: [GitOps](), [Kubernetes](), [Terraform](), [argo-cd](), [ClusterControl](), [Databases](), [opentofu]() Tags: [argo-cd](), [clustercontrol](), [databases](), [gitops](), [hybrid-operations](), [infrastructure](), [kubernetes](), [opentofu](), [sovereign-dbaas](), [terraform]() ### AI overview This article describes a layered GitOps approach for Kubernetes database platforms: manage infrastructure with Terraform or OpenTofu, manage Kubernetes deployments with Argo CD, and standardize operations for operator-managed databases with ClusterControl. It explains how declarative configuration and drift reconciliation differ between Terraform and Argo CD, and compares infrastructure automation options including Atlantis and Flux tf-controller. ### Source excerpt Most platform teams already use GitOps for their Kubernetes apps. The config lives in Git, Argo CD applies it, and deployments are predictable. But look one layer down and things get messy. Infrastructure setup is often still done by hand, running Terraform locally or through scattered scripts. Database operations, especially for databases running through Kubernetes [...] The post Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases appeared first on Severalnines. ## Automate Docker Registry Creation with Harness and Terraform DevFeed: [Automate Docker Registry Creation with Harness and Terraform]() Original publisher: [Read original article]() Author: Shibam Dhar Published: 2026-09-16T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [docker registry](), [Kubernetes](), [Provisioning](), [Terraform](), [Infrastructure as code](), [CI/CD](), [Dockerfile]() Tags: [ci-cd](), [container-image](), [deployment](), [docker-registry](), [infrastructure-as-code](), [kubernetes](), [registry](), [terraform]() ### AI overview A tutorial shows how to use Harness Pipelines and the Harness Terraform Provider to provision a uniquely named Docker Registry, build and push a container image, and deploy it to Kubernetes. It covers Terraform execution in a CI step, passing output variables between stages, and rolling updates with automatic rollback. ### Source excerpt Provision a fresh Docker Registry with Terraform, build your container image into it, and deploy to Kubernetes in one | Blog ## Encore for Python DevFeed: [Encore for Python]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-09-14T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Python](), [FastAPI](), [AWS IAM](), [Amazon Web Services](), [Cloud](), [PostgreSQL](), [Terraform](), [postgresql clusters]() Tags: [aws](), [cloud](), [coding-agents](), [configuration](), [git](), [iam](), [infrastructure](), [postgresql](), [python](), [terraform]() ### AI overview Encore is introducing Encore.py, an upcoming beta that brings Encore's type-safe infrastructure primitives to Python and works alongside frameworks such as FastAPI. The article describes how application-level resource declarations can drive infrastructure provisioning while platform teams retain control over environment-specific settings in AWS, GCP, Terraform, or existing infrastructure. It also highlights preview environments where coding agents can implement and verify features against infrastructure configured to resemble production. ### Source excerpt An early look at Encore for Python, entering beta soon. ## Kubernetes v1.37 brings 67 enhancements. Which matter for operators? DevFeed: [Kubernetes v1.37 brings 67 enhancements. Which matter for operators?]() Original publisher: [Read original article]() Author: Bill Doerrfeld Published: 2026-09-11T17:40:04Z Content type: news Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack](), [The New Stack]() Topics: [Kubernetes](), [Infrastructure as code](), [migration](), [AI Platform](), [Machine learning](), [Authorization]() Tags: [ai](), [ai-infrastructure](), [cloud-native-ecosystem](), [hpe](), [infrastructure-as-code](), [kubecon-cloudnativecon-na-2026](), [kubernetes](), [migration](), [post](), [road-to-kubecon](), [sponsor-hpe](), [sponsored-post](), [terraform]() ### AI overview A Kubernetes roundup covers v1.37 enhancements, HPE Morpheus and Terraform provider changes, migration tooling, and recent CNCF project graduations including Kubeflow. ### Source excerpt Welcome to the first edition of Road to KubeCon, where we'll track the world of Kubernetes as we approach KubeCon The post Kubernetes v1.37 brings 67 enhancements. Which matter for operators? appeared first on The New Stack. ## Terraform AWS Provider Continues Rapid Expansion as AWS Infrastructure Becomes More Complex DevFeed: [Terraform AWS Provider Continues Rapid Expansion as AWS Infrastructure Becomes More Complex]() Original publisher: [Read original article]() Author: Craig Risi Published: 2026-09-11T12:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Terraform](), [Infrastructure as code](), [cloud-infrastructure](), [AWS CloudFormation](), [Amazon Bedrock](), [DSQL]() Tags: [aws](), [cloudformation](), [devops](), [infrastructure-as-code](), [news](), [release](), [terraform](), [terraform-aws-provider-6-62]() ### AI overview Terraform AWS Provider v6.62.0 adds support for AWS services and resources. The article compares Terraform with Pulumi, CloudFormation/CDK, and OpenTofu, and advises teams to pin and test provider upgrades because of schema, state, and behavior risks. ### Source excerpt The Terraform AWS Provider continues its rapid evolution, with v6.62.0 adding support for new AWS capabilities while improving how Terraform understands and manages existing infrastructure. By Craig Risi ## Validating multi-Region DR for Terraform Enterprise with AWS FIS DevFeed: [Validating multi-Region DR for Terraform Enterprise with AWS FIS]() Original publisher: [Read original article]() Author: Frenil Randeria Published: 2026-09-09T21:05:02Z Content type: article Language: en Sources: [AWS Architecture Blog]() Topics: [Terraform](), [AWS Fault Injection Service (FIS)](), [Chaos Engineering](), [Amazon S3](), [Amazon EC2](), [Databases]() Tags: [advanced-300](), [amazon-aurora](), [amazon-ec2](), [amazon-s3](), [aws](), [aws-fault-injection-service-fis](), [disaster-recovery](), [postgresql](), [technical-how-to](), [terraform](), [validation]() ### AI overview This article explains how to validate customer-operated multi-Region disaster recovery for Terraform Enterprise on AWS using three-phase AWS FIS experiments. It covers failover and failback testing, hidden dependency discovery, and reported recovery times of 12-14 minutes. ### Source excerpt Learn how AWS, HashiCorp, and Athenahealth designed and chaos-tested a multi-Region disaster recovery strategy for Terraform Enterprise on AWS. This post walks through three-phase AWS Fault Injection Service experiments across Amazon EC2, Aurora, and Amazon S3, the 12-14 minute recovery times achieved, and the state file dependency pitfall to avoid. ## Security updates for Wednesday DevFeed: [Security updates for Wednesday]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-09T13:04:46Z Content type: news Language: en Sources: [LWN.net]() Topics: [Debian](), [cURL](), [Chromium](), [systemd](), [Terraform](), [.NET]() Tags: [chromium](), [cli](), [debian](), [google](), [intel](), [java](), [kernel](), [opentelemetry](), [python](), [redis](), [security](), [systemd](), [terraform](), [updates]() ### AI overview Security updates have been issued across AlmaLinux, Debian, Fedora, Mageia, Red Hat, SUSE, and Ubuntu for a broad set of packages, including kernels, systemd, Chromium, curl, Python, Java, Terraform provider components, and other system and developer tools. ### Source excerpt Security updates have been issued by AlmaLinux (expat, glib2, microcode_ctl, mrtg, pam, redis, thunderbird, and valkey), Debian (fort-validator, gst-plugins-base1.0, kernel, and slurm-wlm), Fedora (complyctl, libevent, openvpn, and tar), Mageia (dovecot and spice-vdagent), Red Hat (ignition, opentelemetry-collector, and osbuild-composer), SUSE (amazon-ssm-agent, aws-nitro-enclaves-cli, bzip2, cadvisor, chromium, curl, distribution-registry, emacs, freeciv, fuse-overlayfs, gh, google-guest-agent, GraphicsMagick, hauler, insighttoolkit-devel, java-17-openjdk, libidn, libusb-1_0, libvirt, libvncserver, libzypp, zypper, lkl, lxd, multipath-tools, NetworkManager, perl-Net-DNS, perl-URI, python, python-authlib, python-sqlparse, python-tornado, python3, rpcbind, supergfxctl, systemd, terraform-provider-null, ucode-intel, wget, wireshark, and xen), and Ubuntu (curl, ffmpeg, glibc, hsqldb1.8.0, imagemagick, perl, and vim). ## Build full-stack AWS applications in minutes with AI-powered scaffolding DevFeed: [Build full-stack AWS applications in minutes with AI-powered scaffolding]() Original publisher: [Read original article]() Author: Jack Stevenson Published: 2026-09-08T21:24:59Z Content type: article Language: en Sources: [AWS Open Source Blog]() Topics: [App](), [cloud-infrastructure](), [Amazon Bedrock](), [Command-line interface](), [Kiro](), [Terraform](), [Bun]() Tags: [agentic](), [ai](), [ai-coding](), [amazon-bedrock](), [announcements](), [applications](), [aws](), [kiro](), [observability](), [security](), [technical-how-to](), [terraform]() ### AI overview The article introduces version 1.0 of the Nx Plugin for AWS, an open-source set of deterministic Nx generators for scaffolding deployable AWS application components and their infrastructure. It describes using AI assistants or a CLI to generate applications with security, observability, and type-safety practices included, and begins a quick start for an agentic application using Amazon Bedrock. ### Source excerpt AI assistants can stand up an app or website that runs on AWS in minutes. Getting to a production-ready version you would put in front of real customers is still the hard part. Security, observability, type-safety, and resilience are non-negotiable for production. An assistant rarely gets all of that right in one pass, and hardening [...] ## Beyond the Merge: Enforcing Policy Before the Terraform Apply DevFeed: [Beyond the Merge: Enforcing Policy Before the Terraform Apply]() Original publisher: [Read original article]() Author: Sachin Agarwal Published: 2026-09-03T17:25:32Z Content type: article Language: en Sources: [Nirmata]() Topics: [iac-security](), [Terraform](), [Security](), [Kyverno](), [Tooling]() Tags: [ci](), [cloud-security](), [code-security](), [infrastructure-as-code](), [kyverno](), [other](), [policy-as-code](), [pull-request](), [scanner](), [security](), [shift-left](), [terraform]() ### AI overview The article describes using Nirmata Control and its nctl CLI to evaluate Terraform plans against policy-as-code rules before deployment. It presents pre-apply CI checks for detecting infrastructure misconfigurations, including unrestricted ingress, missing S3 public-access blocking, wildcard IAM resources, and missing VPC deployment. ### Source excerpt Run Terraform security scanning on the plan, not the live account. nctl checks 4 critical misconfigs in CI, with exceptions scoped to one resource. ## Harness shipped 58 features in August 2026, including AI code review and agent security scanning DevFeed: [Harness shipped 58 features in August 2026, including AI code review and agent security scanning]() Original publisher: [Read original article]() Author: Chinmay Gaikwad Published: 2026-09-02T18:04:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [Artificial Intelligence](), [AI-assisted coding](), [AI Agent](), [Code review](), [prompt injection](), [Security](), [Terraform]() Tags: [2026](), [ai-code-review](), [code-review](), [coding-agents](), [opentofu](), [prompt-injection](), [security](), [terraform]() ### AI overview Harness describes 58 features released in August 2026, including an agent-scale code repository, AI Code Review, AI Risks scanning for prompt injection and tool poisoning in agent skills, and risk scoring for Terraform and OpenTofu changes. ### Source excerpt Harness shipped 58 features in August 2026: an agent-scale code repository, AI Code Review, AI Risks scanning, and the Blast Radius Agent. | Blog ## MySQL CDC connector for ClickPipes is now Generally Available DevFeed: [MySQL CDC connector for ClickPipes is now Generally Available]() Original publisher: [Read original article]() Author: Marta Paes Published: 2026-09-02T14:03:04Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [MySQL](), [Infrastructure as code](), [Terraform]() Tags: [analytics](), [api](), [clickhouse](), [cloud](), [data](), [infrastructure-as-code](), [mysql](), [observability](), [release](), [terraform]() ### AI overview ClickHouse announces general availability of its MySQL CDC connector for ClickPipes, which replicates MySQL and MariaDB data into ClickHouse Cloud. The release adds automatic parallel snapshotting, reliability and observability improvements, and configuration through the Cloud API and Terraform. ### Source excerpt Replicate MySQL and MariaDB data into ClickHouse Cloud with the generally available MySQL CDC connector, featuring faster parallel snapshots, safer production defaults, improved observability, and infrastructure-as-code support. ## Deploying a RAG Chatbot with Shared State and Storage Across Replicas DevFeed: [Deploying a RAG Chatbot with Shared State and Storage Across Replicas]() Original publisher: [Read original article]() Author: Avi Chawla Published: 2026-09-01T21:11:23Z Content type: tutorial Language: en Sources: [Daily Dose of Data Science]() Topics: [Retrieval-Augmented Generation](), [Kubernetes](), [Terraform](), [FastAPI](), [LangChain](), [Python]() Tags: [fastapi](), [github](), [persistence](), [pgvector](), [python](), [rag](), [retrieval](), [terraform]() ### AI overview The article explains why a RAG chatbot that works locally can lose vector indexes, conversation history, and documents when deployed across multiple replicas. It recommends shared persistence for embeddings, checkpointed conversation state, and shared object storage, with examples using Postgres, pgvector, LangGraph, and object storage. ### Source excerpt + a popular LLM interview question. ## Provision a secure Amazon DocumentDB cluster with Terraform DevFeed: [Provision a secure Amazon DocumentDB cluster with Terraform]() Original publisher: [Read original article]() Author: Sourav Kundu Published: 2026-08-31T20:24:23Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [Amazon DocumentDB](), [iac-security](), [Cryptography](), [passwords]() Tags: [advanced-300](), [amazon-cloudwatch](), [amazon-documentdb](), [amazon-vpc](), [authentication](), [encryption](), [infrastructure-as-code](), [monitoring](), [secrets](), [technical-how-to](), [terraform]() ### AI overview A walkthrough for provisioning a secure Amazon DocumentDB 8.0 cluster with Terraform. It applies infrastructure-as-code security controls including private VPC subnets, TLS, KMS encryption, secrets-managed passwords, security groups, and encrypted monitoring logs. ### Source excerpt Learn how to provision a secure Amazon DocumentDB cluster using Terraform. This post applies infrastructure-as-code best practices with encryption, AWS Secrets Manager authentication, network isolation, and encrypted monitoring. ## 9 things to consider before choosing an IaC platform in 2026 DevFeed: [9 things to consider before choosing an IaC platform in 2026]() Original publisher: [Read original article]() Author: Jonah Kowall Published: 2026-08-26T14:33:56Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Infrastructure as code](), [Architecture & Design](), [Provisioning](), [Cloud](), [Terraform]() Tags: [2026](), [ci](), [cloud](), [evaluation](), [iac](), [infrastructure](), [infrastructure-as-code](), [opentofu](), [policy](), [terraform](), [workflows]() ### AI overview This 2026 article presents nine considerations for evaluating an infrastructure as code platform. It emphasizes that mature IaC now involves coordinating changes, managing access, enforcing policies, reviewing infrastructure changes, and keeping environments synchronized--not only provisioning cloud resources. It recommends assessing whether a platform is necessary, examining its execution layer and scalability, testing it under concurrent workloads and failures, and ensuring that engineers beyond the platform builder can use it effectively. ### Source excerpt IaC platform evaluation in 2026: nine things to test, from execution and dependency handling to policy enforcement, support quality and AI workflows. ## Start here: Azure SQL Foundations series DevFeed: [Start here: Azure SQL Foundations series]() Original publisher: [Read original article]() Author: Anna Hoffman Published: 2026-08-25T16:00:18Z Content type: article Language: en Sources: [Developer Blogs]() Topics: [Azure SQL](), [Microsoft](), [migration](), [Artificial Intelligence](), [Azure OpenAI](), [DevOps](), [GitHub](), [Retrieval Augmented Generation (RAG)](), [API](), [MCP Server]() Tags: [ai](), [azure](), [azure-openai](), [azure-sql](), [devops](), [github](), [guide](), [how-to](), [json](), [langchain](), [mcp](), [microsoft-for-developers](), [migration](), [powershell](), [rag](), [terraform]() ### AI overview Microsoft introduces the Azure SQL Database Foundations series, a set of four videos covering Hyperscale databases, modernization and migration, AI features, and operational data. Each episode includes a repository for hands-on follow-up. ### Source excerpt Most developers I talk to aren't asking whether Azure SQL Database can handle their next app. They're asking where to start when it comes to modernization, migration, and AI in the database. If you're reading this, you're probably in a similar boat: you've got an existing schema or databases, a scaling question you haven't had [...] The post Start here: Azure SQL Foundations series appeared first on Microsoft for Developers. ## Announcing support for ClickStack in the ClickHouse Terraform provider DevFeed: [Announcing support for ClickStack in the ClickHouse Terraform provider]() Original publisher: [Read original article]() Author: Jordan Simonovski Published: 2026-08-14T16:03:36Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Terraform](), [observability](), [dashboards]() Tags: [clickhouse](), [dashboards](), [infrastructure](), [observability](), [open-source](), [production](), [review](), [self-hosted](), [terraform](), [workflow]() ### AI overview The ClickHouse Terraform provider adds beta support for managing ClickStack resources in self-hosted deployments and ClickHouse Cloud. Dashboards, alerts, sources, saved searches, connections, and webhooks can be stored in version control, reviewed, and applied through an infrastructure workflow. ### Source excerpt The ClickHouse Terraform provider now manages ClickStack dashboards, alerts, sources, and webhooks, putting observability config in version control. ## Best Kubernetes Infrastructure as Code Tools in 2026 DevFeed: [Best Kubernetes Infrastructure as Code Tools in 2026]() Original publisher: [Read original article]() Author: Pulumi Content Team Published: 2026-08-14T00:00:00Z Content type: comparison Language: en Sources: [Pulumi]() Topics: [Infrastructure as code](), [Kubernetes](), [Terraform](), [argo-cd](), [Helm charts](), [GitOps](), [flux](), [opentofu](), [Amazon EKS](), [AWS CloudFormation](), [VPC](), [AWS IAM]() Tags: [argo-cd](), [cloudformation](), [code](), [comparisons](), [devops](), [flux](), [general](), [gitops](), [helm](), [helm-charts](), [iam](), [infrastructure](), [infrastructure-as-code](), [kubernetes](), [opentofu](), [platform-engineering](), [terraform](), [vpc]() ### AI overview This comparison explains that Kubernetes infrastructure as code spans cluster and cloud provisioning, in-cluster workload definition, and continuous delivery and reconciliation. It presents Pulumi and Terraform or OpenTofu as general-purpose provisioning options, Helm and Kustomize for workload templating, and Argo CD and Flux for GitOps reconciliation. ### Source excerpt There is no single best Kubernetes infrastructure as code tool, because "Kubernetes IaC" actually spans three different jobs. For provisioning the cluster and its cloud dependencies, Pulumi and Terraform (or OpenTofu) are the strongest general-purpose options. For templating and packaging workloads, Helm and Kustomize dominate. For continuous reconciliation once things are running, Argo CD and Flux lead the GitOps category. The right stack usually combines one tool from each layer, not a single tool that claims to do all three. What counts as infrastructure as code for Kubernetes? Kubernetes infrastructure as code work splits into three layers that get conflated constantly, and the confusion is where most tool comparisons go wrong. The cluster and cloud layer provisions the things Kubernetes itself sits on top of: the managed control plane (EKS, GKE, AKS), node pools, the VPC and subnets, IAM roles, load balancers, and cluster add-ons. Terraform, Pulumi, and cloud-native tools like CloudFormation operate here. The in-cluster workload layer defines what runs on the cluster once it exists: Deployments, Services, ConfigMaps, CustomResourceDefinitions, and the Helm charts or Kustomize overlays that template them. This is where Helm, Kustomize, and Crossplane's custom resources live. The delivery and reconciliation layer keeps what's declared in Git in sync with what's actually running on the cluster, continuously, rather than as a one-shot apply. Argo CD and Flux own this layer, and they consume the output of the other two rather than replacing them. Most real Kubernetes platforms use tools from at least two of these layers together. A team might provision EKS with Terraform, package its application with Helm, and let Argo CD reconcile it continuously. Knowing which layer a tool actually addresses, rather than treating "Kubernetes IaC" as one shopping list, is the first decision that matters. Pulumi provisions the cluster and the workloads on it in the same language Pul ## Compatibility Testing Pulumi HCL DevFeed: [Compatibility Testing Pulumi HCL]() Original publisher: [Read original article]() Author: Ian Wahbe Published: 2026-08-14T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Testing](), [opentofu](), [Terraform](), [terraform provider](), [Code]() Tags: [code](), [engineering](), [hcl](), [opentofu](), [terraform](), [terraform-provider](), [testing]() ### AI overview The article explains a compatibility-testing approach for Pulumi HCL. It defines correctness as Pulumi HCL and OpenTofu generating the same Terraform provider steps from the same HCL program, then describes tests that compare provider configuration and RPC behavior. ### Source excerpt Pulumi HCL has at its core a simple promise: A program that works for tofu apply will also work for pulumi up. This must be true to allow Terraform modules to be shared between tofu config and Pulumi programs. This property makes testing Pulumi HCL simple. Let me explain. At the end of the day, Pulumi is a system to translate actual state & desired state into a series of imperative actions, so actual state can be reconciled to desired state. Terraform is a system to translate actual state & desired state into a series of imperative actions, so actual state can be reconciled to desired state. How desired state is expressed can be radically different, and the underlying reconciliation engine can be radically different, but at the end of the day, both tools do the same thing: Executing a Terraform program looks like this: flowchart LR tf["*.tf files"] current["current state"] subgraph engine["reconciliation engine"] direction LR desired["desired state"] --> internal["provider steps"] end output["provider steps"] tf --> desired current --> engine engine --> output Executing a Pulumi program is more dynamic, because the reconciliation engine is in more active dialog with the user's program. That said, the diagram is the same shape. To match semantics, Pulumi HCL dynamically bridges any Terraform provider in the registry. This means that, for the subset of Pulumi programs that are valid OpenTofu programs, both programs take the same input (*.tf files) and produce the same step output (Terraform provider steps). Providers are the part of our model that generates user-observable behavior, which means if we match what providers see, we match what users see. This gives us a really nice definition of correctness for Pulumi HCL1: Pulumi HCL correctly interprets an HCL program when it generates the same set of provider steps as tofu does. If you are familiar with property-based testing, you might be thinking this looks like a testable property. You're right. How we compatibility ## Avoid Azure secret rotation with secretless authentication DevFeed: [Avoid Azure secret rotation with secretless authentication]() Original publisher: [Read original article]() Author: Cody Murray-Bruce; Ben Johnson-Staub Published: 2026-08-12T00:00:00Z Content type: tutorial Language: en Sources: [Datadog | The Monitor blog]() Topics: [Azure](), [Authentication](), [Entra ID](), [OpenID connect (OIDC)](), [telemetry](), [Terraform](), [migration]() Tags: [authentication](), [azure](), [cli](), [entra-id](), [identity-and-access-management](), [infrastructure-monitoring](), [integration](), [microsoft](), [migration](), [oidc](), [secrets](), [telemetry](), [terraform]() ### AI overview This article explains how Datadog's secretless authentication for Azure replaces long-lived client secrets with federated identity using Microsoft Entra ID and OpenID Connect. It describes the short-lived token flow and configuration or migration options through Quickstart, Terraform, the Azure CLI, or the Azure portal. ### Source excerpt Learn how secretless authentication for Datadog's Azure integration helps prevent telemetry interruptions that result from expired client secrets. ## DevOps Automation Platform Explained: Why You Need One DevFeed: [DevOps Automation Platform Explained: Why You Need One]() Original publisher: [Read original article]() Author: Eric Minick Published: 2026-08-11T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [DevOps](), [Automation](), [Deployment](), [Artificial Intelligence](), [ci](), [Provisioning](), [Terraform](), [Ansible](), [Incident response]() Tags: [ai](), [ansible](), [automation](), [ci](), [deployment](), [devops](), [incident](), [monitoring](), [provisioning](), [security](), [terraform]() ### AI overview This article explains how a DevOps automation platform connects build, test, deployment, security, provisioning, incident response, and rollback workflows. It contrasts an integrated, workflow-aware platform with separate automation tools such as Ansible, CI runners, and Terraform, and describes AI-native capabilities including test selection, failure diagnosis, anomaly detection, and auto-remediation. ### Source excerpt What is a DevOps automation platform and why does your team need one? How deployment automation, AI, and automated DevOps speed up delivery. | Blog ## ScyllaDB Customer Experience Spotlight: Susie Solis DevFeed: [ScyllaDB Customer Experience Spotlight: Susie Solis]() Original publisher: [Read original article]() Author: Cynthia Dunlop Published: 2026-08-10T14:28:35Z Content type: article Language: en Sources: [ScyllaDB]() Topics: [Databases](), [distributed-systems](), [cloud-infrastructure](), [Kubernetes](), [Terraform](), [Latency](), [Linux]() Tags: [blog](), [cloud-infrastructure](), [community](), [customer](), [cx-profiles](), [database](), [distributed-systems](), [kubernetes](), [latency](), [linux](), [on-call](), [production](), [streaming](), [support](), [terraform]() ### AI overview Susie Solis, a ScyllaDB Technical Support Engineer, discusses her background in technical support, cloud infrastructure, and distributed systems, along with a Kubernetes and Terraform project built to reproduce environments and troubleshoot customer issues. She also describes ScyllaDB's ability to sustain high-throughput production workloads and low latency during major streaming events. ### Source excerpt Meet Susie Solis, a Technical Support Engineer on the Customer Experience team here at ScyllaDB. ## Developer Self-Service Forms Are Dead: Here's What Comes Next DevFeed: [Developer Self-Service Forms Are Dead: Here's What Comes Next]() Original publisher: [Read original article]() Author: Revital Ben Ami Published: 2026-08-10T11:32:54Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Artificial Intelligence](), [Terraform](), [GitHub](), [Amazon EC2](), [Amazon EKS]() Tags: [agents](), [ai](), [ai-agents](), [developer](), [github](), [infrastructure](), [policy](), [terraform](), [workflows]() ### AI overview The article argues that static developer self-service forms create maintenance costs, fail to handle edge cases, and ask developers infrastructure questions they may not be able to answer. It proposes context-aware AI agents that can interview developers, inspect existing resources, apply organizational policies, and generate infrastructure outputs through Terraform modules and GitHub workflows. ### Source excerpt Static self-service forms can't reason. See how context-aware AI agents replace them with dynamic, policy-driven golden paths. ## Terraform Scalability: When IaC Outgrows Your Setup DevFeed: [Terraform Scalability: When IaC Outgrows Your Setup]() Original publisher: [Read original article]() Author: Mrinalini Sugosh Published: 2026-08-10T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Terraform](), [Infrastructure as code](), [Scalability](), [iac-security]() Tags: [dynamodb](), [harness](), [iac](), [s3](), [scalability](), [security](), [terraform]() ### AI overview This article examines how Terraform scalability challenges emerge as infrastructure code and teams grow. It discusses bottlenecks involving state management, collaboration, governance, large state files, locking, plan times, module sprawl, and version drift, and introduces Harness IaCM as a management solution. ### Source excerpt Terraform scalability issues slow teams down. Learn how to overcome IaC bottlenecks with better management. See how Harness helps. | Blog ## Instrument serverless apps with agentic onboarding DevFeed: [Instrument serverless apps with agentic onboarding]() Original publisher: [Read original article]() Author: Rohan Agarwal; Piyali Banerjee Published: 2026-08-10T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [Serverless](), [AWS Lambda](), [azure container apps](), [Cloud Run](), [Command-line interface](), [MCP Server](), [Artificial Intelligence](), [Claude Code](), [cursor](), [Node.js](), [Terraform]() Tags: [agentic](), [ai](), [aws](), [aws-lambda](), [azure](), [azure-container-apps](), [claude-code](), [cli](), [cursor](), [google-cloud](), [google-cloud-run](), [mcp-server](), [node](), [serverless](), [serverless-monitoring](), [terraform]() ### AI overview Datadog's agentic onboarding helps instrument serverless applications across AWS Lambda, Google Cloud Run, and Azure Container Apps. Developers can use an AI assistant connected through the Datadog MCP Server or run the AI Setup CLI to inspect projects, adapt setup to existing deployment tools and runtimes, and prepare configuration changes for review. ### Source excerpt Use Datadog agentic onboarding to instrument AWS Lambda, Google Cloud Run, and Azure Container Apps from an AI assistant or CLI. [Next page]()