New: Versioned CLI and SDK Docs

Terraform State Management Best Practices for Enterprise Teams

Terraform state management is critical for enterprise teams running infrastructure at scale. Local state is unsuitable for production due to lack of collaboration, no locking, and security risks. Best practices covered include using remote backends (S3, Azure Storage, GCS, Terraform Cloud), enabling state locking with DynamoDB, separating state per environment, encrypting state files, enabling versioning for rollback, modularizing infrastructure to keep state files small, implementing RBAC, and running Terraform through CI/CD pipelines rather than developer machines. A checklist and common mistakes section round out the guidance.

Preventing agent-generated infrastructure bloat through spec-driven governance

AI engineer agents can generate Terraform, Kubernetes manifests, and Dockerfiles at scale, but without sustainability constraints in the specification, they systematically reproduce over-provisioned infrastructure patterns. The post argues that sustainability must be a first-class constraint at the specification level — before agents generate a single line of IaC — rather than an operational fix applied after deployment. Three high-impact domains are identified: cloud resource provisioning (e.g., oversized GKE node types), Kubernetes pod resource requests (set to arbitrary safe values instead of measured p95 utilization), and container base image selection (full Ubuntu/Debian instead of distroless/Alpine). Enforcement is achieved through four pipeline stages: constrained spec generation, static analysis tools (Checkov, tfsec, KICS, Trivy), blocking quality gates in CI/CD, and runtime telemetry feeding back into constraint refinement. Practical starting steps include auditing existing IaC specs for sustainability defaults, adding a single blocking Checkov policy, and embedding constraints before agentic pipelines scale.

Amazon EVS VCF 9.0 and 9.1 support

Amazon Elastic VMware Service (EVS) now supports VMware Cloud Foundation (VCF) versions 9.0 and 9.1. Users can run VCF software directly within Amazon VPC on EC2 bare-metal instances, maintaining full control over installation, operations, and management. AWS also launched a Solutions for EVS GitHub repository with examples, templates, and infrastructure as code artifacts to help users get started. The update is available in all regions where Amazon EVS is offered.

Spacelift Intelligence Now Deploys Modules Straight From Your Module Registry

Spacelift Intelligence's Intent feature can now deploy modules directly from your Spacelift module registry using plain language commands. Developers can request modules by name without knowing slugs or writing Terraform blocks. Intent handles version resolution, input validation, policy checks, and background execution. Updates and upgrades are conversational — changing inputs or upgrading versions doesn't require restating existing configuration. Deletions respect the dependency graph and registry integrity. Deployed modules appear as first-class resources with full audit history, state management, and governance policy evaluation.

Amazon SageMaker Unified Studio now supports Terraform for provisioning

Amazon SageMaker Unified Studio giờ đây hỗ trợ triển khai thông qua Terraform nhờ module mã nguồn mở terraform-aws-sagemaker-unified-studio, cho phép các nhóm nền tảng triển khai các domain SageMaker dưới dạng Infrastructure as Code (IaC) có kiểm soát phiên bản, tích hợp với CI/CD.

Lập trình viên nên đọc bài này để tìm hiểu cách tự động hóa triển khai và quản lý môi trường SageMaker Unified Studio với Terraform, giúp tiết kiệm thời gian và tránh sai sót trong cấu hình IAM, domain, và pipeline CI/CD.

How to Test Infrastructure as Code

A comprehensive guide to testing infrastructure as code with Pulumi, covering all three testing layers: unit tests using mocked cloud providers (no credentials needed, runs in milliseconds), integration tests that deploy real resources via the Automation API, and policy-as-code checks that enforce compliance rules on every preview and deploy. Complete runnable examples are provided in Python, TypeScript, Go, C#, and Java. The guide also compares Pulumi's testing approach to Terraform (Terratest and terraform test), highlighting language cohesion as a key advantage — infrastructure, tests, and policies all written in the same general-purpose language using familiar test frameworks like pytest, Mocha, and go test.

Automating cloud infrastructure with Cursor

Encore tích hợp với Cursor để cho phép các tác nhân AI khai báo và cung cấp cơ sở hạ tầng đám mây (cơ sở dữ liệu, hàng đợi, cron jobs, v.v.) trực tiếp trong mã ứng dụng Go hoặc TypeScript, loại bỏ các tệp Terraform hoặc cấu hình riêng biệt. Các thay đổi và yêu cầu cơ sở hạ tầng của chúng sẽ được quản lý cùng nhau trong một pull request duy nhất, với môi trường preview tự động được cung cấp theo mỗi PR.

Lập trình viên nên đọc bài này để khám phá cách tự động hóa triển khai cơ sở hạ tầng đám mây một cách liên kết chặt chẽ với mã nguồn, giảm thiểu rủi ro và phức tạp khi quản lý các file cấu hình tách biệt.