aws-nuke
terraform-aws-eks-blueprints
aws-nuke | terraform-aws-eks-blueprints | |
---|---|---|
86 | 39 | |
5,353 | 2,509 | |
2.4% | 2.9% | |
8.0 | 9.1 | |
3 days ago | 5 days ago | |
Go | HCL | |
MIT License | Apache License 2.0 |
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.
terraform-aws-eks-blueprints
-
I am afraid to spin up an EKS instance using AWS provider
Have you checked out this repo https://github.com/aws-ia/terraform-aws-eks-blueprints
-
Deploy Secure Spring Boot Microservices on Amazon EKS Using Terraform and Kubernetes
Now that you have the networking part done, you can build configurations for the EKS cluster and its add-ons. You will use the terraform-aws-modules to create the EKS cluster and eks_blueprints module from terraform-aws-eks-blueprintsto configure EKS add-ons.
-
Enabling GPU Nodes for PyTorch Workloads on EKS with Autoscaling
## (https://github.com/aws-ia/terraform-aws-eks-blueprints) ## ... [other Terraform code] ## Cluster Configuration module "eks" { # ... [other configuration] self_managed_node_groups = { gpu_node_group = { node_group_name = "gpu-node-group" ami_type = "AL2_x86_64_GPU" capacity_type = "ON_DEMAND" instance_types = [ "g4dn.xlarge", "g4dn.2xlarge", ] # ... [other configuration] taints = { dedicated = { key = "nvidia.com/gpu" value = "true" effect = "NO_SCHEDULE" } } # ... [other configuration] } } }
- Why is there no consistency in the EKS examples.
-
Is there any advantage to running Karpenter and CordDNS in Fargate?
Here is the link: https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/main/examples/karpenter/main.tf
- Need suggestions for managing eks terraform module
-
What's everyone's favorite EKS Terraform module these days?
Anyone using eks blueprints or cloudposse's module?
- How are most EKS clusters deployed?
-
Ideal setup for EKS deployment?
Take a look at the EKS Blueprints for Terraform as a place to start. I know the team is working on their v5 release which should be a solid improvement. https://github.com/aws-ia/terraform-aws-eks-blueprints/milestone/1
-
How do you initially upload your docker image to an ECR
Take a look at the EKS Blueprints for Terraform v5 rewrite for more details. However, EKS Blueprints for Terraform (v4 as it is today) is pretty darn good _if_ you just want to manage basic charst like load balancer controller and Karpenter. It provisions IAM Roles and Policies along with Helm charts all in one easy set-up. It's just not something I'd want to touch with more complex use cases and we'll see how the EKS Blueprints team does with the v5 rewrite - their direction looks reasonable, but Terraform just isn't really designed for the problem it's trying to solve there, so it's going to be somewhat clunky one way or another.
What are some alternatives?
cloud-nuke - A tool for cleaning up your cloud accounts by nuking (deleting) all resources within it
terraform-aws-eks - Terraform module to create AWS Elastic Kubernetes (EKS) resources 🇺🇦
former2 - Generate CloudFormation / Terraform / Troposphere templates from your existing AWS resources.
cdk-eks-blueprints - AWS Quick Start Team
savepagenow - A simple Python wrapper and command-line interface for archive.org’s "Save Page Now" capturing service
eksctl - The official CLI for Amazon EKS
infracost - Cloud cost estimates for Terraform in pull requests💰📉 Shift FinOps Left!
terraform-aws-ecs-container-definition - Terraform module to generate well-formed JSON documents (container definitions) that are passed to the aws_ecs_task_definition Terraform resource
LocalStack - 💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
terraform-aws-eks-cloudwatch-logs - Terraform module for deploying AWS Fluent Bit as a daemonSet to send logs to CloudWatch Logs aws-for-fluent-bit inside a pre-existing EKS cluster.
aws-budget-alarms - AWS Budget alarms with AWS Chatbot sending alarms to slack
terraform-aws-eks-cluster - Terraform module for provisioning an EKS cluster