botocore VS AWS SDK for Ruby

With some searching, you can sometimes get an idea of what’s to come in the future. AWS’s SDKs are intended to be used with all AWS partitions, supporting all the partitions and regions. By examining the Python SDK (boto) code , we can infer that two more partitions may be in progress.

More correctly would likely be https://github.com/boto/botocore/issues/1543

Pretty much all of the SDKs refer to a standard set of JSON files that define the APIs, in a much older internal format ("C2J") than anything like Smithy or OpenAPI. You can find these in most SDK repos today, e.g. boto3: https://github.com/boto/botocore/blob/develop/botocore/data/kms/2014-11-01/service-2.json

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: