pulumi-aws
terracognita
Our great sponsors
| pulumi-aws | terracognita | |
|---|---|---|
| 3 | 14 | |
| 419 | 2,093 | |
| 3.4% | 2.7% | |
| 9.5 | 3.4 | |
| about 14 hours ago | 10 days ago | |
| Go | Go | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pulumi-aws
-
HashiCorp Adopts Business Source License
Sure, but the providers for some of the biggest platforms are maintained by HashiCorp[1] - like the AWS, Azure, GCP, and Kubernetes providers[2], and it appears the Pulumi AWS provider (for example) _does_ use the Terraform AWS provider, even to this day[3].
1. https://developer.hashicorp.com/terraform/registry/providers... - "official" providers are maintained by HashiCorp
2. https://registry.terraform.io/browse/providers?tier=official - The filtered list of "official" providers maintained by HashiCorp
3. https://github.com/pulumi/pulumi-aws/tree/008c4360bc9fc24303... - Just prove it to myself, I can see the `upstream` git submodule, which embeds pulumi/terraform-provider-aws, which is a fork of hashicorp/terraform-provider-aws, although the repo was not created as a fork in Github, so it is not marked as a "fork" and so I have to compare commit histories to tell that it is a fork.
-
Converting Full Terraform Programs to Pulumi
>Isn't pulumi aws just terraform under the hood still?
It depends.
The AWS "Classic" provider uses the terraform provider [1].
The AWS "Native" provider does not, and instead uses the AWS Cloud Control API [2].
[1]: https://github.com/pulumi/pulumi-aws
[2]: https://github.com/pulumi/pulumi-aws-native
-
For IaC: Pulumi or Terraform?
Pulumi uses terraform providers to schematize the CRUD options for some cloud providers. Part of the difficulty with any infrastructure as code offering is that your favourite cloud provider doesn't always provide a full API spec, so we need to somehow figure out what resources can be created, what parameters are available to those resources etc. We take the terraform provider, look at the available operations for that provider and then turned it into a Pulumi schema, which can then be read by the Pulumi engine. If you take a look here you can actually see that generated schema for AWS.
terracognita
- Generate Terraform code from your existing cloud infrastructure
-
Strategies for converting an existing deployment to IaC?
I haven't worked with any of the ones that purport to work with AWS, but a quick Google shows terraformer and Terracognita as options - maybe look into trying those out?
-
Monthly 'Shameless Self Promotion' thread - 2023/05
We also contribute to the open-source community with projects like InfraMap, that generate your infra diagram on the fly based on your tfstate or the most famous TerraCognita, a reverse Terraform.
-
Importing multiple modules at once from AWS
You can use tools like https://github.com/cycloidio/terracognita or https://github.com/iann0036/former2 to generate the terraform code for you. Then you can consolidate them and if they are simply the same type of objects with different values then you can use terragrunt to pass values to your terraform module.
- Is it possible to import existing infrastructure into Terraform then redeploy it without semantic representation?
-
terracognita - --tags syntax for aws?
https://github.com/cycloidio/terracognita/compare/master...fg-322 should fix it
-
Tools like terraformer
Terracognita
- Existing AWS resource to HCL?
-
Deactivated SFTP servers from AWS transfer family but still getting charged - can you delete a server but still save all configurations/settings somewhere to spin it up easily later?
If you still want to go that way, stuff like the import command and terracognita exist. There's more solutions out there, those are just what came to mind immediately.
What are some alternatives?
doctl - The official command line interface for the DigitalOcean API.
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
humbug - Get usage metrics and crash reports for your API, library, or command line tool.
former2 - Generate CloudFormation / Terraform / Troposphere templates from your existing AWS resources.
pulumi-kubernetes - A Pulumi resource provider for Kubernetes to manage API resources and workloads in running clusters
terraboard - :earth_africa: :clipboard: A web dashboard to inspect Terraform States
pulumi-eks - A Pulumi component for easily creating and managing an Amazon EKS Cluster
Azure-Terraform-Scripts - Terraform scripts on Azure for Windows and Linux VM's
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
inframap - Read your tfstate or HCL to generate a graph specific for each provider, showing only the resources that are most important/relevant.
EBS-Optimizer - Source code of the initial version of the EBS Optimizer tool made available on the AWS Marketplace.
azure-terrafy-handsonlab - Azure Terrafy hands on lab