In a recent blog post, HashiCorp announced the full release of Terraform Cloud, an open-source SaaS platform for teams to manage their infrastructure-as-code workflows. This orchestration takes place through cloud-agnostic tools that allow teams to improve their productivity through repeatable automation. This announcement follows their May 2019 announcement of Remote State Management.
Terraform 0.12 is a major update that includes dozens of improvements and features spanning the breadth and depth of Terraform’s functionality. First-class expression syntax: express references and expressions directly rather than using string interpolation syntax. Generalized type system: use lists and maps more freely, and use resources as object values.
Iteration constructs: transform and filter one collection into another collection, and generate nested configuration blocks from collections. Structural rendering of plans: plan output now looks more like configuration making it easier to understand.
We are excited to announce the HashiCorp Terraform Enterprise Module Registry, a service catalog that provides organizations with a self-service workflow to provision any infrastructure. As organizations deploy more workloads in cloud, operations teams have to ensure that every team in the organization follows safe and efficient provisioning practices. This is best addressed with a service catalog with hardened infrastructure modules.
This service catalog allows IT operators to codify, collaborate, and publish modular templates for provisioning cloud infrastructure that can be used by developers or other operators across large organizations.
It’s easy to run HashiCorp Terraform on your laptop and go wild managing your infrastructure. But what do you do when you start working on more complex arrangements in a large, complex organization? At that point, the problem is not scaling infrastructure, but scaling your working practices to support a large landscape of teams and applications as well as scalingyour workflows to enhance collaboration within your team and between teams.
Recently a question got asked on Hacker News that grabbed my attention. I wanted to know how others’ experience has been. At ACL, we have multiple Lambda functions that we heavily rely on, and we use Terraform to deploy them.
It’s been working well for us, so I was curious to know how others have approached Lambda. However, it seemed that others were struggling: In short, I was left wondering “why don’t people simply use Terraform?
In the following tutorial you can learn how to implement container security as code. You probably have a CI/CD pipeline to automatically rebuild your container images. What if you could define your container security as code, push it into a Git repository to version control changes and then enforce your policy in your container orchestration tool like Docker or Kubernetes using Sysdig Secure?
Terraform is an awesome tool to deploy and update your infrastructure using code.
I am excited to announce the public-release of modules.tf, which allows a conversion from visual AWS diagrams using cloudcraft.co to infrastructure code using Terraform. Resources with arguments once specified during creation of diagrams are present in infrastructure code. Most popular EC2 types of resources are supported, more will be added in the future.
VPC, Security group, Autoscaling Group, RDS, ELB, ALB, SNS, SQS, EC2 instances are implemented already. Many of relations between resources and their dependencies are respected in infrastructure code.