# infrastructure-as-code Published articles for infrastructure-as-code. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Sunsetting netlab Vagrant/libvirt provider DevFeed: [Sunsetting netlab Vagrant/libvirt provider]() Original publisher: [Read original article]() Published: 2026-09-17T05:51:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Vagrant](), [Infrastructure as code](), [Orchestration](), [Containerlab topology](), [Oracle-VM-VirtualBox]() Tags: [change](), [containers](), [infrastructure](), [infrastructure-as-code](), [netlab](), [orchestration](), [vagrant](), [virtualbox]() ### AI overview The netlab project is sunsetting its Vagrant/libvirt provider after the vagrant-libvirt plugin became effectively unmaintained and HashiCorp announced the closure of Vagrant Cloud by the end of 2026. Existing support and tests will remain for now, but no new libvirt features or device integration tests are planned; containerlab will become the primary orchestration path. ### Source excerpt When I started the netlab project, Vagrant was the go-to tool if you wanted to build a virtual environment described in a text configuration file (an idea popularized as infrastructure-as-code). It wasn't ideal for what we were doing, but a tool rarely does a great job when used far away from its intended use case. netlab initially supported Vagrant with VirtualBox, quickly adding support for KVM/libvirt through the vagrant-libvirt plugin. Life was good... until it wasn't. Read more ... ## Article: Your Next DSL Author Is a Language Model DevFeed: [Article: Your Next DSL Author Is a Language Model]() Original publisher: [Read original article]() Author: Irakli Betchvaia Published: 2026-09-16T11:00:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [Large Language Model](), [Infrastructure as code](), [Retrieval Augmented Generation (RAG)](), [Code](), [Fable]() Tags: [ai](), [ai-ml-data-engineering](), [article](), [artificial-intelligence](), [benchmarks](), [development](), [domain-specific-languages](), [dsls](), [hallucinations](), [infrastructure-as-code](), [large-language-model](), [large-language-models](), [ml-data-engineering](), [next-dsl-author-language-model](), [validation]() ### AI overview The article introduces Typed Domain Grounding (TDG), which embeds a domain-specific language as a typed internal DSL in a mainstream host language. It argues that compiler type errors and generate-compile-repair loops can reduce syntactic hallucinations in language-model output. A benchmark reported higher Structural Fidelity and lower hallucination rates than two lenient external DSLs, although first-try compile rates were lower and results varied by model. ### Source excerpt In this article, the author introduces Typed Domain Grounding, an approach to reducing LLM hallucinations in domain-specific languages by embedding them in mainstream typed languages. Using kUML benchmarks and an infrastructure-as-code example, he explores how compiler validation and generate-compile-repair loops can make model-generated DSL output more reliable. By Irakli Betchvaia ## 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 ## GitLab Dedicated: Compliance for a new regulatory era DevFeed: [GitLab Dedicated: Compliance for a new regulatory era]() Original publisher: [Read original article]() Author: Aathira Nair Published: 2026-09-14T00:00:00Z Content type: article Language: en Sources: [GitLab]() Topics: [GitLab](), [Software as a service](), [Amazon Web Services](), [Cybersecurity](), [Security](), [Resilience](), [Deployment](), [Testing](), [Multitenancy]() Tags: [amazon-web-services-aws](), [aws](), [compliance](), [deployment](), [gdpr](), [gitlab](), [infrastructure-as-code](), [nis2](), [product](), [regulatory](), [resilience](), [saas](), [security](), [testing]() ### AI overview The article presents GitLab Dedicated as a fully isolated, single-tenant SaaS platform hosted and managed by GitLab in a preferred Amazon Web Services region. It explains how the service is intended to help European enterprises address compliance, data sovereignty, audit readiness, security, resilience, and operational responsibilities related to DORA, NIS2, and GDPR. ### Source excerpt Enforcements such as NIS2 are no longer a future planning consideration. The European Union Agency for Cybersecurity's (ENISA) NIS360 report confirms that supervisory authorities are actively assessing cybersecurity maturity across critical sectors. The agency is moving from guidance and consultation into active oversight, scrutiny, and accountability. This is the regulatory environment European enterprises now operate in. Multi-tenant cloud platforms remove operational overhead but place source code and pipelines on shared infrastructure regulators now scrutinize. Self-managed solutions provide isolation but transfer responsibility for upgrade cycles, security patches, and disaster recovery (DR) tests to an already stretched platform team. Both deployment options leave gaps in risk management, data sovereignty, and furnishing audit evidence. In this article, you'll discover how GitLab Dedicated, a fully isolated, single-tenant SaaS solution deployed in your preferred Amazon Web Services (AWS) region and hosted and managed by GitLab, addresses these challenges and helps you keep pace with evolving compliance requirements. "NatWest Group is adopting GitLab Dedicated SaaS to enable our engineers to use a common cloud engineering platform; delivering new customer and colleague outcomes rapidly, frequently, and securely with high quality, automated testing, on-demand infrastructure, and straight-through deployment." -- Adam Leggett, Platform Lead for Engineering Platforms, NatWest Group Regulations are driving change In the European Union, key regulations are driving the need for a different platform approach. These regulations converge on a decision most enterprises made before they existed: a platform their developers build on. That decision now carries audit consequences it didn't before. Digital Operational Resilience Act (DORA), which came into force across EU financial services in January 2025, requires financial institutions to keep critical technology resilient, ## 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 ## Why the AWS PACE Team Built Its Full-Stack Scaffolding as an Nx Plugin DevFeed: [Why the AWS PACE Team Built Its Full-Stack Scaffolding as an Nx Plugin]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2026-09-10T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [Amazon Web Services](), [coding](), [AI-assisted coding](), [Infrastructure as code](), [Template]() Tags: [ai](), [aws](), [blog](), [coding](), [coding-agents](), [devkit](), [generators](), [infrastructure-as-code](), [nx](), [plugin](), [tutorial](), [video]() ### AI overview The article explains why the AWS PACE team built full-stack scaffolding as an Nx plugin using Nx Devkit generators. It discusses predictable prototyping, generated code ownership, infrastructure and application components, and how coding agents affect plugin development. ### Source excerpt How the AWS PACE team built the Nx Plugin for AWS on the Nx Devkit, and why coding agents make building your own Nx plugin cheaper than ever. ## Self-Hosted Platform Build Order: Dependencies from Bare Metal to Model Serving DevFeed: [Self-Hosted Platform Build Order: Dependencies from Bare Metal to Model Serving]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-04T07:00:00Z Content type: article Language: en Sources: [Philipp Lehmann]() Topics: [Self-hosted](), [Ansible](), [Kubernetes](), [ceph](), [observability](), [model-serving](), [Compose]() Tags: [ansible](), [architecture](), [article](), [ceph](), [compose](), [infrastructure-as-code](), [kubernetes](), [model-serving](), [observability](), [self-hosted]() ### AI overview This article explains the dependency order for building a self-hosted platform. It covers consistent bare-metal inventory, Ansible configuration convergence, networking, Kubernetes, Ceph storage, identity, observability, and model serving. ### Source excerpt Self-hosted platform build order: why mesh, cluster, Ceph storage, identity and observability must precede model serving, shown with Compose depends_on. ## 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. ## 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. ## 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. ## Troubleshoot and secure your code faster with Datadog's Bitbucket Cloud Source Code integration DevFeed: [Troubleshoot and secure your code faster with Datadog's Bitbucket Cloud Source Code integration]() Original publisher: [Read original article]() Author: Eric Metaj; Mark Azer Published: 2026-08-31T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [Developer Tools](), [iac-security](), [Vulnerabilities]() Tags: [apm](), [bitbucket](), [ci-visibility](), [cloud](), [code](), [code-profiling](), [code-security](), [devsecops](), [error-tracking](), [infrastructure-as-code](), [integration](), [observability](), [open-source](), [pull-requests](), [secret-scanning](), [security](), [software-delivery](), [test-optimization](), [vulnerabilities]() ### AI overview Datadog's Bitbucket Cloud Source Code integration links selected repositories with Datadog so teams can investigate production issues with source context and review security findings before merging code. ### Source excerpt Connect Bitbucket Cloud to Datadog to troubleshoot with source code in context and surface test, quality, and security feedback in pull requests. ## Testing Infrastructure Code by Executing Its Real Expressions DevFeed: [Testing Infrastructure Code by Executing Its Real Expressions]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-28T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [Ansible](), [Testing](), [Pytest](), [Ansible Roles]() Tags: [ansible](), [ci-cd](), [code](), [infrastructure](), [infrastructure-as-code](), [pytest](), [testing]() ### AI overview This article explains how to test Ansible infrastructure code by rendering the shipped Jinja expression through Ansible's actual templating machinery. It recommends extracting the expression from the role file, using realistic fixture variables, and asserting on the rendered result instead of duplicating the computation in Python. ### Source excerpt Ansible Templar in pytest: render the shipped combine(recursive=True) expression from defaults/main.yml instead of a shallow Python paraphrase. ## Neo Security: Securing Infrastructure in the Agentic Era DevFeed: [Neo Security: Securing Infrastructure in the Agentic Era]() Original publisher: [Read original article]() Author: Joe Duffy Published: 2026-08-28T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [pulumi-neo](), [Security](), [cloud-infrastructure](), [Artificial Intelligence](), [Infrastructure as code](), [Static code analysis]() Tags: [agent](), [agentic](), [ai](), [aws](), [azure](), [cloud-infrastructure](), [infrastructure-as-code](), [kubernetes](), [product](), [pulumi](), [pulumi-neo](), [security]() ### AI overview Pulumi is opening a research preview of Neo Security, an agent that analyzes cloud infrastructure for exploitable flaws. It builds a threat model, maps attack paths, and produces an actionable security posture report, including for infrastructure provisioned across AWS, Azure, Google Cloud, and Kubernetes. ### Source excerpt Recently, AI systems have started turning up exploitable flaws in code that survived decades of human review. The frontier labs have released useful tools to help uncover many of these flaws through agent-led static code analysis. This is a huge leap ahead, but cloud infrastructure has many exploitable flaws that code analysis alone cannot find. These flaws are often as severe as the ones in code, or worse, and they await discovery by malicious agents on offense. We realized recently we can uniquely help here. At Pulumi, we have complete visibility into your entire cloud estate: infrastructure resources, their semantics, connections and dependencies between them, runtime logs and information, and more -- and have built an entire context graph out of them that is accessible to agents. Thanks to large language models, the cost of analyzing that full context graph is no longer prohibitive. As a result, today we're opening a research preview of Pulumi Neo Security. Neo Security is an agent that can find exploitable flaws in your cloud infrastructure. It starts with a threat model of your cloud estate, and then works systematically through every potential point of attack. The result is a security posture report that is immediately actionable thanks to Pulumi's infrastructure as code technology. Neo Security works on your existing infrastructure regardless of how it was provisioned, across any of our thousands of cloud providers including AWS, Azure, Google Cloud, and Kubernetes. We're releasing it in research preview to begin, so we can work closely with customers to run and address any findings. If you'd like to give it a try, contact us. How it finds attack paths Neo Security's aim is to provide a high-confidence, actionable security posture report. It gets there in three passes. The first builds a threat model, before it looks for anything. It works out what your crown jewels are, which resources are accessible to outside actors, which accounts hold production data, wh ## Break-glass access for Amazon EKS when federated identity fails DevFeed: [Break-glass access for Amazon EKS when federated identity fails]() Original publisher: [Read original article]() Author: Sam Mukherjee Published: 2026-08-26T16:20:28Z Content type: article Language: en Sources: [Containers]() Topics: [Amazon EKS](), [AWS Identity and Access Management (IAM)](), [Infrastructure as code](), [MFA](), [Authorization](), [iac-security](), [migration]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [aws-iam](), [best-practices](), [identity-and-access-management](), [infrastructure-as-code](), [mfa](), [migration](), [technical-how-to]() ### AI overview This post presents a break-glass access pattern for Amazon EKS clusters when a federated identity provider fails. It describes a dedicated cross-account IAM role with enforced, recency-aware MFA, infrastructure-as-code templates, validation tests, and post-incident recovery procedures. ### Source excerpt Implementing break-glass access for Amazon EKS clusters removes the circular dependency where a federated identity provider outage locks you out of the clusters you need to reach to fix it. This post supplies a cross-account IAM role with enforced MFA, infrastructure-as-code templates, validation tests, and a post-incident recovery procedure. ## 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. ## Introducing public preview runtimes on AWS Lambda, starting with Node.js 26 and Python 3.15 DevFeed: [Introducing public preview runtimes on AWS Lambda, starting with Node.js 26 and Python 3.15]() Original publisher: [Read original article]() Author: Jonathan Tuliani Published: 2026-08-15T14:09:35Z Content type: news Language: en Sources: [AWS Compute Blog]() Topics: [AWS Lambda](), [Node.js](), [Python](), [Amazon Web Services]() Tags: [announcements](), [availability](), [aws](), [aws-lambda](), [benchmarking](), [china](), [foundational-100](), [govcloud](), [infrastructure-as-code](), [node-js](), [python](), [release]() ### AI overview AWS Lambda introduces public preview runtimes for Node.js 26 and Python 3.15, allowing developers to test upcoming language versions before general availability and provide feedback while breaking changes remain possible. ### Source excerpt AWS Lambda introduces public preview runtimes, a new way to try upcoming language versions before GA. Start using Node.js 26 and Python 3.15 today, provide feedback, and help shape runtime quality before general availability. ## 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 ## Deploy MCP Servers on AWS Lambda with Serverless Framework v4 DevFeed: [Deploy MCP Servers on AWS Lambda with Serverless Framework v4]() Original publisher: [Read original article]() Author: Serverless Team Published: 2026-08-11T00:00:00Z Content type: tutorial Language: en Sources: [Serverless Blog]() Topics: [MCP](), [AWS Lambda](), [serverless framework](), [Streaming]() Tags: [aws](), [aws-lambda](), [cloud-computing](), [faas](), [function-as-a-service](), [infrastructure-as-code](), [mcp](), [news](), [pricing](), [serverless](), [serverless-architecture](), [serverless-framework](), [streaming](), [yaml]() ### AI overview A Serverless Framework v4.41.0 deployment workflow for MCP servers on AWS Lambda, using YAML and providing an HTTPS endpoint, response streaming, and pay-per-request pricing. ### Source excerpt Serverless Framework v4.41.0 deploys MCP servers to AWS Lambda in a few lines of YAML - a real HTTPS endpoint, response streaming, and pay-per-request pricing. ## DevOps vs Platform Engineering & Software Platforms DevFeed: [DevOps vs Platform Engineering & Software Platforms]() Original publisher: [Read original article]() Author: Eric Minick Published: 2026-08-11T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [DevOps](), [Platform Engineering](), [Software Engineering](), [CI/CD](), [Infrastructure as code](), [Monitoring](), [Artificial Intelligence]() Tags: [ai](), [ci-cd](), [devops](), [infrastructure-as-code](), [monitoring](), [platform-engineering](), [policy-as-code](), [self-service](), [software-engineering]() ### AI overview This article explains how DevOps and platform engineering address different parts of software delivery. It describes DevOps as a culture and set of practices, while platform engineering provides internal tooling and self-service infrastructure to make those practices repeatable at scale. It also discusses when platform engineering becomes useful, how software engineering platforms combine both approaches, and why AI increases the need for governed self-service and policy-as-code. ### Source excerpt DevOps vs platform engineering: what is the difference? Learn how they relate, when to use each, and how a software engineering platform combines both. | Blog ## Top 15 Kubernetes Consulting Companies in 2026: Choosing the Right Partner for Cloud-Native Success DevFeed: [Top 15 Kubernetes Consulting Companies in 2026: Choosing the Right Partner for Cloud-Native Success]() Original publisher: [Read original article]() Author: Urolime Technologies Published: 2026-08-10T18:15:31Z Content type: comparison Language: en Sources: [Kubernetes Archives - Urolime Blogs]() Topics: [Kubernetes](), [Cloud Native Ecosystem](), [Architecture & Design](), [migration](), [Platform Engineering](), [Security]() Tags: [2026](), [architecture](), [cloud-migration](), [cloud-native](), [consulting](), [infrastructure-as-code](), [kubernetes](), [kubernetes-consulting](), [operational]() ### AI overview A guide to 15 Kubernetes consulting companies in 2026, describing why businesses use consulting services and the capabilities to assess when selecting a partner. It covers Kubernetes architecture, application migration, security, multicloud operations, platform engineering, GitOps, observability, governance, and cost optimization. ### Source excerpt The question isn't whether you should use Kubernetes or not, rather its on how to make use of Kubernetes to add value to your business. From AI-based applications and microservices to multicloud as well as edge computing, Kubernetes is at the center of digital transformation. But implementing and managing Kubernetes solutions requires a set of [...] ## Terraform and Kubernetes: A Practical Guide for 2026 DevFeed: [Terraform and Kubernetes: A Practical Guide for 2026]() Original publisher: [Read original article]() Author: Pulumi Content Team Published: 2026-08-07T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Kubernetes](), [Terraform](), [Provisioning](), [Testing](), [Artificial Intelligence]() Tags: [ai](), [ai-agents](), [deployment](), [general](), [guide](), [infrastructure-as-code](), [kubernetes](), [platform-engineering](), [provisioning](), [terraform](), [testing]() ### AI overview A practical guide to using Terraform with Kubernetes, covering the Kubernetes provider, provisioning workflows, testing, policy, deployment, and the role of AI agents. It explains limitations including provider ordering and the need for Kubernetes API access during planning. ### Source excerpt Yes, Terraform can manage Kubernetes: the official hashicorp/kubernetes provider lets you declare Deployments, Services, and other objects as HCL resources, and community providers like kubectl fill in the gaps. It works well for many teams. The friction shows up around two well-documented limits -- provider ordering and plan-time API access -- and around testing, where a general-purpose language changes what's possible. That friction matters more in 2026 than it did a few years ago. Kubernetes infrastructure now sits next to AI-driven engineering workflows: agents that propose changes, run previews, and open pull requests need infrastructure code they can read, test, and reason about with the same tools they use for application code. A cluster definition written in HCL and a workload definition written in YAML are both harder for an agent -- and a person -- to unit test, refactor, or type-check than the equivalent in TypeScript, Python, or Go. This guide is about the operating model for Kubernetes infrastructure: how the cluster, the platform layer, and the workloads on top of it get provisioned, tested, and shipped. It's a different question from "should I write my Kubernetes manifests in YAML, HCL, or a real language," which we cover in detail in YAML, Terraform, or Pulumi: what's the smart choice for deployment automation with Kubernetes? Read that post first if you're deciding how to author manifests; read this one for the wider workflow -- provisioning, testing, policy, and where AI agents fit. How does Terraform manage Kubernetes today? The hashicorp/kubernetes provider (current release v3.2.1, requiring Terraform 1.0.0 or later) is the primary path, and teams typically combine it with one or two others depending on what they're deploying: Approach What it's for Notes Typed resources (kubernetes_deployment_v1, kubernetes_service_v1, etc.) Core, well-known object types Full HCL validation and typed attributes for the objects the provider models explicitly kubernete ## Infrastructure Control Plane | Day 2 Operations & Drift DevFeed: [Infrastructure Control Plane | Day 2 Operations & Drift]() Original publisher: [Read original article]() Author: Nicole Morgan Published: 2026-08-06T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Infrastructure as code](), [Software-defined networking](), [Provisioning](), [Ansible](), [CI/CD](), [configuration](), [Amazon EC2](), [AWS CloudFormation](), [Amazon Web Services]() Tags: [ansible](), [aws](), [ci-cd](), [cloudformation](), [configuration](), [deployment](), [ec2](), [incident](), [infrastructure](), [infrastructure-as-code](), [provisioning](), [systems](), [tools]() ### AI overview This article explains that infrastructure problems often emerge during day 2 operations, after initial deployment. It describes how console changes, incidents, and isolated Terraform, Ansible, and CI/CD workflows create infrastructure drift, and argues that control planes can enforce governance, detect divergence, and automate remediation. ### Source excerpt Learn why infrastructure breaks after deployment and how control planes enforce governance, detect drift, and automate remediation across Terraform, Ansible, an | Blog ## Pulumi Cloud Adds Terraform Backend Support for Agentic Infrastructure DevFeed: [Pulumi Cloud Adds Terraform Backend Support for Agentic Infrastructure]() Original publisher: [Read original article]() Author: Daniel Perlovsky Published: 2026-08-04T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Terraform](), [Infrastructure as code](), [opentofu](), [Cloud](), [Deployment]() Tags: [agentic](), [agents](), [ai-agents](), [cloud](), [deployment](), [enterprise](), [hcl](), [iac](), [infrastructure-as-code](), [opentofu](), [platform](), [product](), [pulumi-cloud](), [terraform]() ### AI overview Pulumi announces general availability of Pulumi Cloud as a backend for Terraform state. The release supports existing Terraform deployment patterns while adding Pulumi Cloud capabilities such as remote runs, visibility, manual approvals, and scalable access management. ### Source excerpt At Pulumi, we are building the platform for agentic infrastructure. Pulumi Cloud provides the guardrails and enterprise readiness needed to safely move fast in this new era. While we are seeing extraordinary adoption -- over 40% of our users now manage infrastructure using AI agents -- we know many organizations are at different phases in their AI journey and have to balance building for the future with maintaining their existing infrastructure as code (IaC) solutions like Terraform. Today, we are launching three ways that Pulumi lets you avoid trading off building for the future against building for today. You don't have to rip out Terraform to enter the agentic era. Pulumi Cloud brings agentic infrastructure to the IaC estate you already have. What we're shipping today Last December, our CEO Joe Duffy laid out his vision to make Pulumi the platform for all of your infrastructure as code. The capabilities we are launching today make that promise a reality. Pulumi is now fully interoperable with Terraform and OpenTofu and enables organizations to build upon their existing IaC estate rather than starting from scratch as they work toward the agentic infrastructure future. Pulumi Cloud as a Terraform backend We are excited to announce the general availability of Pulumi Cloud as the backend to your Terraform state, enabling organizations to seamlessly lift and shift their existing Terraform estates. We recognize there is lots of infrastructure that works as is, and switching over to a new management paradigm may not always be possible. Pulumi Cloud support for the Terraform state backend lets organizations maintain their existing Terraform deployment patterns while also unlocking the power of Pulumi Cloud. The following common patterns for running Terraform are now supported: Plans and applies run remotely by default for new Terraform stacks, following the behavior of HCP Terraform and Terraform Enterprise. When you run a Terraform operation, it executes on a Pulumi-hoste [Next page]()