Add short name for region in describe_regions() or describe_endpoints()

[bgupta]

Describe the feature

I find myself frequently using the shorthand abbreviations for regions that were popularized by availability zone "Zone IDs" e.g. use1 for us-east-1. I'd like a way to have this available in boto3.

Use Case

I commonly use the short name in cost optimization datasets. The short names are also commonly embedded in pricing data, so being able to have that maintained in the boto3 library would be a great help.

Proposed Solution

Extend https://github.com/boto/botocore/blob/develop/botocore/data/endpoints.json to have another dictionary key as well as decribe_endpoints.

Other Information

One could grunt through DescribeAvailabilityZones using regex and splits and such to potentially get these mapping, but it's very unclean.

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

SDK version used

boto3 1.28.53, botocore 1.31.53

Environment details (OS name and version, etc.)

Ubuntu 20.04, Python 3.11.5

[indrora]

You can use the EC2 call describe_availability_zones to get a list of the AZs in a region: https://docs.aws.amazon.com/ram/latest/userguide/working-with-az-ids.html

Since these aren't guaranteed to be consistent account to account (e.g. use1-az1 could be us-east-1b or us-east-1c, for example), I doubt we'll be hardcoding them into the Endpoints file. However, I could see an interface to turn an AZ Id into a full identifier later on.

[RyanFitzSimmonsAK]

Hey, thanks for this feature request and for your patience. The team has no plans to implement this feature. As you and indrora both mentioned, DescribeAvailabilityZones provides both ZoneId and RegionName, so that's the intended way you can map these.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.