Include Supported Regions for PropertyTypes and ResourceTypes

[ScriptAutomate]

Issue

AWS documentation seems to be out-of-sync across a variety of places when it comes to:

• What AWS services are supported in each region
• What AWS services are supported by AWS CloudFormation in each region

Instead, it exists across a spectrum of sources that can contradict each other at times:

• AWS Region Table
• AWS Service Pricing
• AWS CFN Resource Specification Files
• AWS Announcements (ex. "...the following regions are supported for this new service...")
• AWS Documentation (ex. "...the following regions are supported for this service...")

Proposed Solution

For AWS CloudFormation, the source-of-truth seems to be the AWS CloudFormation Specification Files (also seen here, but the "source" hasn't been updated to reflect production since March 2019: markdown source and currenlty referenced in issues like #426 ).

I have an auditing repository, AWS CloudFormation Resource Specification Auditor, that has generated a JSON containing what resources / properties are supported by what regions: ScriptAutomate/aws-cfn-resource-specs/blob/master/supported-regions-per-resource.json

If the CFN docs workflow has something similar to what I'm doing with the proof-of-concept tool, aws-doc-region-updater.py (could be split into functions and cleaned up), the docs can automatically contain the latest supported region information at each ResourceSpecificationVersion release.

[PatMyron]

@ScriptAutomate I have found the pricing information to be closest to the truth. Unfortunately, this is obviously insufficient because it provides no regional availability information for features that are provided free of charge.

[ScriptAutomate]

@PatMyron Though I closed #491, I do see that there are instances of PropertyType not existing in CFN spec files, in certain regions, even if the ResourceType parent exists within that region.

I've been working on a human readable changelog generator (created from a separate machine-readable changelog), and see that this is the case with certain items missing from us-east-1 (I haven't done any larger audits for instances of a resource where property types are missing): v8-CHANGELOG.md

I could tweak my CFN User Guide doc editor to just target ResourceType types for now, to append supported region lists to ResourceType docs, but these instance look like it means either one or both of these are present problems:

• PropertyType values are missing that should be present when their ResourceType parent is present
• PropertyType values are missing in certain regions, for certain ResourceType parents, because the PropertyType is not yet supported in the region

[ScriptAutomate]

As an added note, my project can potentially assist with this (here are some example commands):

• https://github.com/ScriptAutomate/aws-cfn-resource-specs#example-use-case

The above links to example commands that can quickly audit whether they are known as supported by all regions (and if not, which regions support them). It is based on audit results of all the available CFN resource specs.

[joshbean]

Closing this issue or pull request in advance of archiving this repo. For more information about the decision to archive this repo (and others in the 'awsdocs' org), see the announcement on the AWS News Blog.