Feat: Support All AWS Partitions

[joel-aws]

This PR extends support of moto to all AWS Partitions.

One can see all Partitions, Regions, and DNS Suffixes with: curl https://raw.githubusercontent.com/boto/botocore/develop/botocore/data/endpoints.json | jq '.partitions[] | [.partitionName, .partition, .regions, .dnsSuffix]'

[bblommers]

Hi @joel-aws, thanks for the PR! Please see my comment

[joel-aws]

I realized I was querying an old endpoints.json, so I just added the most recent DNS Suffixes.

[codecov]

Codecov Report

Merging #6412 (1dcf3e1) into master (932b7a2) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #6412   +/-   ##
=======================================
  Coverage   96.16%   96.16%           
=======================================
  Files         799      799           
  Lines       77906    77917   +11     
=======================================
+ Hits        74920    74932   +12     
+ Misses       2986     2985    -1     

Flag	Coverage Δ
servertests	36.93% <28.57%> (-0.01%)	⬇️
unittests	96.11% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
moto/core/base_backend.py	93.78% <100.00%> (+0.66%)	⬆️

... and 3 files with indirect coverage changes

[bblommers]

LGTM - thanks again @joel-aws!

[github-actions]

This is now part of moto >= 4.1.12.dev36

[bblommers]

Hi @joel-aws!

Another followup question/issue around this feature:
The get_available_regions() will be potentially deprecated by the AWS SDK team - see aws/aws-sdk#206 (comment)

The suggested alternative way to get this region-information is to use the SSM parameter store instead, and I am looking into a feasible implementation for Moto.

The main problem I am running into is that these ISO regions are not exposed in the SSM parameter store. The US-gov and China regions are exposed, so it would make sense to me if the ISO-regions are also part of it.

Is that something you can raise internally, to see if that information can be included/exposed? I understand that it's probably an entirely different team responsible for this, but I'm assuming that a request from an internal employee would hold more weight than a random support ticket from a regular user 🙂

[joel-aws]

@bblommers -- apologies for the delay in responding!

I am now posing this question internally... On the flip side, we value customer input via service tickets. If you haven't already opened one, could you do that and share the ticket # ?

[bblommers]

No problem @joel-aws - thanks for getting back to me.

I haven't been on top of this either, to be honest - I only just opened a ticket now, nr 171584385800169.