aws-elastic-beanstalk-cli-setup VS LocalStack

git clone https://github.com/aws/aws-elastic-beanstalk-cli-setup.git

Some people do not like working on the web interface. They prefer command line and the black screen. Elastic Beanstalk provides a powerful command line utility. Open the GitHub Repository. That gives you detailed instructions about how to clone the repository and run the script to install the CLI.

$ sudo apt install python3.8-venv $ sudo apt install pipx $ pipx install virtualenv installed package virtualenv 20.14.1, Python 3.8.10 These binaries are now globally available - virtualenv done! ✨ 🌟 ✨ $ git clone https://github.com/aws/aws-elastic-beanstalk-cli-setup.git $ python3 ./aws-elastic-beanstalk-cli-setup/scripts/ebcli_installer.py Success!

First you need to install EB CLI. Follow instructions there to install it using script. If for some reason it's not working (i.e. you're using Arch linux), follow the procedures there.

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.