The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Top 10 terraform-aw Open-Source Projects
-
digger
Digger is an open source IaC orchestration tool. Digger allows you to run IaC in your existing CI pipeline ⚡️
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
modules.tf-lambda
Infrastructure as code generator - from visual diagrams created with Cloudcraft.co to Terraform
-
terraform-aws-nat-instance
Terraform module to provision a NAT Instance using an Auto Scaling Group and Spot Instance from $1/month
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
terraform-aws-bootstrap
Setup Terraform remote state in the S3 backend (with DynamoDB locking) for AWS
-
Terraform-IAAC
This repository will give you a lot of examples about Infrastructure as a code using Terraform
Project mention: Ask HN: Should we build support for more CI platforms, or features for Actions? | news.ycombinator.com | 2024-04-03Currently, Github Actions is de-facto the only fully supported CI platform in Digger, we’ve been building it as a CI-agnostic tool (https://github.com/diggerhq/digger) from get go. We keep getting requests to support more CI systems on our community slack and over Github issues (https://github.com/diggerhq/digger/issues/81).
Unlike other automation tools for Terraform, Digger doesn’t run jobs on the server; instead it uses your CI (like Actions) as a compute backend. This is more secure and also much cheaper if you use your own runners in your CI.
But each CI and each VCS is ever so slightly different; and we are now at a crossroads - Should we build support for more CI platforms, or more features for GitHub Actions? We’d love any thoughts/inputs!
Maybe cloudcraft https://www.cloudcraft.co
Project mention: Terraform best practices for reliability at any scale | news.ycombinator.com | 2023-08-04> At scale, many Terraform state files are better than one. But how do you draw the boundaries and decide which resources belong in which state files? What are the best practices for organizing Terraform state files to maximize reliability, minimize the blast-radius of changes, and align with the design of cloud providers?
1000% agree. I put together my version of standing up remote state in AWS in Github. https://github.com/aryounce/terraform-aws-bootstrap
Our use of Terraform splits state exactly as described primarily to keep the state refresh times reasonable.
terraform-aws related posts
-
How to Not Use Secrets
-
Do we even need Infrastructure Visualization Tools?
-
Auto architecture diagram of AWS
-
AWS Discovery Service - for AWS Services, Not On Prem
-
Which good (and free) software to create a diagram of an AWS network?
-
Sample cost details report
-
Visualization/mapping tool?
-
A note from our sponsor - WorkOS
workos.com | 30 Apr 2024
Index
What are some of the best open-source terraform-aw projects? This list will help you:
Project | Stars | |
---|---|---|
1 | digger | 2,670 |
2 | wrongsecrets | 1,117 |
3 | terraform-tuesdays | 384 |
4 | modules.tf-lambda | 346 |
5 | terraform-aws-nat-instance | 169 |
6 | k3s-aws-terraform-cluster | 139 |
7 | k8s-aws-terraform-cluster | 75 |
8 | terraform-aws-bootstrap | 12 |
9 | terraform-aws-db | 12 |
10 | Terraform-IAAC | 10 |
Sponsored