LocalStack VS eks-anywhere

Later you can use any S3 compatible storage because the code I write will still work, but for testing purposes on my local machine, I will use LocalStack:

Acesse o site da LocalStack e faça login.

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.

(For others who hadn't heard of it: localstack is

LocalStack Website

O Localstack: https://localstack.cloud/, é um recurso que possibilita simular diversos recursos AWS (dynamoDB, s3, iam, cognito, ses), dentro da sua máquina, utilizando o docker.

I'd suggest move from rancher to EKS Anywhere and the respective Cluster API providers... Self-managed node pools on top of bottlerocket can be established using common terraform-aws-eks module, otherwise.

There are plenty of vendor specific bugs, like no EBS in [EKS Fargate](https://github.com/aws/containers-roadmap/issues/1113), and settling a Kubernetes cluster on top of Bottlerocket and [EKS Anywhere](https://github.com/aws/eks-anywhere), on your own is somewhat impossible.

To get started with Amazon EKS Anywhere on bare metal, visit the documentation site. To learn more about Amazon EKS Anywhere, visit the product page.

> It has no init system.

Apologies that I can't link directly to the "--init" flag but docker actually does have an init, it's just (err, was?) compiled into the binary: https://docs.docker.com/engine/reference/commandline/run/#op...

My recollection is that it either adopted, or inspired, https://github.com/Yelp/dumb-init#readme which folks used to put into their Dockerfile as the init system back in the day

Folks (ahem, I'm looking at you, eks-anywhere[0]) who bundle systemd into a docker container are gravely misguided, and the ones which do so for the ability to launch sshd alongside the actual container's main process are truly, truly lost

0: https://github.com/aws/eks-anywhere/issues/838#issuecomment-...

EKS anywhere looks like an adventure - https://anywhere.eks.amazonaws.com

That brings us to the end of this walkthrough. Thank you very much for reading and I hope you will give EKS Anywhere a spin. The complete documentation is available here. If you are interested in contributing, please open an issue or pull request on the EKS Anywhere GitHub repo. Let me know your thoughts in the comments below. If you have more questions, feel free to reach out to me on LinkedIn or Twitter.

First class integration and support by most of the cloud providers (DOKS, AKS (Which has been opensourced))