terraform-aws-icons
terraforming
terraform-aws-icons | terraforming | |
---|---|---|
1 | 9 | |
40 | 4,298 | |
- | - | |
0.0 | 1.6 | |
over 4 years ago | over 2 years ago | |
Python | Ruby | |
MIT License | 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.
terraform-aws-icons
-
DevOps tools you should have on your belt
𝌸 cfn-diagram will visualise CloudFormation templates as diagrams. To take static screenshots of generated diagrams from cfn-diagram you can use the extension cfn-diagram-ci. Terraform already has the functionality for generating architecture diagrams by default, but if you need AWS icons in the architecture diagram you have to add an extension such as terraform-aws-icons must be used.
terraforming
- Importing multiple modules at once from AWS
-
Tools like terraformer
Terraforming
- Copy Azure resources via terraform
- Existing AWS resource to HCL?
-
Where to start with a mess?
I would also strongly recommend an iterative triage process: don't feel that you need to solve everything all once. It's a huge amount of progress if you can get to a stage where you understand the relationships between services, have enough monitoring to identify failures, and can iteratively move services to more granular IAM policies even if it's all still running in one big account. Simply using a tool like terraformer or terraforming to move the manual configuration into an IaC workflow is an accomplishment, especially since it helps you both make changes more confidently and identify where new changes are still being made. Depending on the politics, that last part might be important: you'll be unpopular if you take away everyone's rights but you'll probably have better luck first nudging people to make them using a sensible flow rather than by hand.
-
Just starting out with terraform. Doubts wrt existing infra.
Haven't tried this but if I ever find myself in your situation I'll give it a spin https://github.com/dtan4/terraforming
-
Continuous Infrastructure Deployment with Terraform Cloud
There are a couple of tools to automate creating terraform configuration and prepopulate state from existing resources, like terraforming, terraformer or cf-terraforming. But it is still cumbersome and laborious and in my experience, it's usually way easier to just recreate everything within terraform from scratch wherever that's possible.
- Current infrastructure as code
-
DevOps tools you should have on your belt
🧪 Terraforming export existing AWS resources to Terraform style (tf, tfstate).
What are some alternatives?
saml2aws - CLI tool which enables you to login and retrieve AWS temporary credentials using a SAML IDP
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
cfn-python-lint - CloudFormation Linter
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
sls-dev-tools - Dev Tools for the Serverless World - Issues, PRs and ⭐️welcome!
former2 - Generate CloudFormation / Terraform / Troposphere templates from your existing AWS resources.
awsume - A utility for easily assuming AWS IAM roles from the command line.
cf-terraforming - A command line utility to facilitate terraforming your existing Cloudflare resources.
AWSConsoleRecorder - Records actions made in the AWS Management Console and outputs the equivalent CLI/SDK commands and CloudFormation/Terraform templates.
aws-toolkit-vscode - Amazon Q, CodeCatalyst, Local Lambda debug, SAM/CFN syntax, ECS Terminal, AWS resources
aws-codebuild-docker-images - Official AWS CodeBuild repository for managed Docker images http://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref.html