aws-nuke
former2
aws-nuke | former2 | |
---|---|---|
86 | 11 | |
5,353 | 2,140 | |
2.4% | - | |
8.0 | 7.6 | |
3 days ago | about 2 months ago | |
Go | JavaScript | |
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.
aws-nuke
-
Cutting down AWS cost by $150k per year simply by shutting things off
To give this a slightly different spin:
--> "The best optimization is simply not spinning things up."
At least for local development and testing, as made possible by LocalStack (https://localstack.cloud), among other local testing solutions and emulators.
We've seen so many teams fall into the trap of "someone forgot to shut down dev resource X for a week and now we've racked up a $$$ bill on AWS".
What is everyone's strategy to avoid this kind of situation? Tools like `aws-nuke` (https://github.com/rebuy-de/aws-nuke) are awesome (!) to clean up unused resources, but frankly they should not be necessary in the first place.
-
I am afraid to spin up an EKS instance using AWS provider
We use nuke aws at work to remove any leftovers: https://github.com/rebuy-de/aws-nuke
-
Route 53 Billing
You can use this tool on github to nuke all resources.
- Need Help to Control Rising Costs of Elastic Cloud on AWS
-
Best sandbox environment to learn AWS
There's this. I haven't used it myself, but it looks to be pretty effective: https://github.com/rebuy-de/aws-nuke
-
Enterprise-scaled Self-Healing StackSets
At this scale, operations can take a lot of time, because there are multiple operational tasks that we need to do when AWS accounts are leaving the AWS Organization or Teams are nuking the AWS account, StackSets Instances get drifted, because not all required resources for compliance can be secured ( SCP Limitations ), existing AWS accounts are joining the AWS Organization and all mandatory StackSets needs to be deployed, and manual steps should be reduced to a minimum. Furthermore, there is no feature from the Service itself to gain an overview of the status of drifted Instances and the general health of your StackSet health and compliance.
-
AWS - development environment
Since you're using CDK already, have a way to configure the deployment of the whole thing to a per-developer test account; that's still gonna cost you, but you can bundle everything in an organization / organizational unit for billing purposes, and you can also schedule https://github.com/rebuy-de/aws-nuke to run nightly to clean these accounts from longer-running resources.
-
Does your org create/destroy per-project AWS accounts?
And by extension, https://github.com/rebuy-de/aws-nuke as well.
-
I want to terminate my account but i cant delete this last VPC, what should i do? I dont want to be billed anymore!
I can also recommend aws-nuke which is an easy to way to destroy in your account.
-
Weekly: Share your EXPLOSIONS thread
nothing blew up accidentally this week, but our team at kubefirst is falling more and more in love with aws-nuke. it's an open source command line tool that lets you basically reset an aws account back to an empty state. if you have an environment where you regularly practice your platform provisioning, you probably know that failed destroys while iterating on orchestration can leave junk behind pretty easily. aws-nuke has been so nice to be able to blow away everything in an aws account - and then we just run terraform in the account to get all our core infra back afterward. nice allowlist filters and dryrun detail work too. check them out.
former2
-
Top 10 terraform tools you should know about.
Former2 is a tool that automates the creation of Infrastructure-as-Code (IaC) scripts from existing AWS resources. It utilizes the AWS JavaScript SDK to scan the user’s AWS infrastructure, identifying all available resources. Users can then select from this list which resources they want to include in their IaC outputs. This process simplifies the task of writing IaC scripts, especially for complex environments, by directly converting current AWS configurations into ready-to-use code. Former2 is particularly useful for documenting existing infrastructure or for migrating manually created resources into an IaC framework.
-
[Question] Cloud formation Template Import Resources tools
More info: https://github.com/iann0036/former2
- former2
-
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 there a way to turn a existing cloudformation template into a terraform file?
-
Overwhelmed by AWS
I have never tried out this tool, but maybe it's worth checking: you could create all the stuff via AWS Console in a sandbox environment and then try to use former2. Nothing autogenerated will ever be good enough compared to handcrafted, but it should give you a nice starting point without much effort.Such a tool can not be expected to work reliably. Thankfully, you need to cover only classic, foundational services like EC2, ELB, and IAM, so I would expect them to work properly for those use cases.
-
how reliable is it to generate a cloud formation automatically from an existing AWS environment?
Author of Former2 here.
-
Disaster Recovery with Former2?
I've heard of a few people setting up pipelines that use the CLI with the `ALL` services option to generate inventories of their systems, but the generated template would almost certainly not work out of the box due to:
- tool to log into AWS and generate Terraform code
-
Current infrastructure as code
Not quite: a command line tool is also available: https://github.com/iann0036/former2/blob/master/cli/README.md
What are some alternatives?
cloud-nuke - A tool for cleaning up your cloud accounts by nuking (deleting) all resources within it
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
savepagenow - A simple Python wrapper and command-line interface for archive.org’s "Save Page Now" capturing service
terracognita - Reads from existing public and private cloud providers (reverse Terraform) and generates your infrastructure as code on Terraform configuration
infracost - Cloud cost estimates for Terraform in pull requests💰📉 Shift FinOps Left!
terraforming - Export existing AWS resources to Terraform style (tf, tfstate) / No longer actively maintained
LocalStack - 💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
aws-multi-account-viewer - Serverless app designed for any customer with two or more accounts to view resources across accounts/regions in simple single pane of glass website
aws-budget-alarms - AWS Budget alarms with AWS Chatbot sending alarms to slack
driftctl - Detect, track and alert on infrastructure drift
aws-account-vending-machine - This repository contains various versions of the account vending machine used to provision AWS accounts with custom configurations