LocalStack VS AWS SDK for Ruby

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.

In Ruby 3.2, "Fill.exists" was removed. brew will automatically install the most recent version of Ruby when you perform a brew install cocoapods, which is why you encounter this problem.

To those looking for this information officially, you can get it from the JSON files that describe every API that is in the SDK. Here's a link to that subtree in the Ruby SDK. You could write a parser to go through all the JSON files and grab this information, which is probably what others did.

Ruby SDK: https://github.com/aws/aws-sdk-ruby/pull/2553

Finally, for the purpose of this series, you will need to have installed Ruby, as well as the AWS SDK for Ruby.

AWS Lambda supports seven different languages in which you can code, including Ruby. Here, we will be using AWS Ruby-sdk to connect to DynamoDB.

We can re-use the same EC2 client stub response because Aws::EC2::Resource#instances implementation it's just a wrapper around the Aws::EC2::Client#describe_instances method, so the underlying EC2 API call is the same. Snippet code from https://github.com/aws/aws-sdk-ruby: