In the event of AWS introducing a new region, there may be a delay in when the CloudHealth platform incorporates the new region into assets collection and reporting.
Expected behavior is no collection of assets and metrics from that region until support is configured:
1. Assets will either not appear in CloudHealth or, if they did, it will have stale info
2. 'No data' recommendation in the rightsizing report
3. Reservation details would be stale (Stale is defined as up to 6 hours behind the actual usage/event of the charge because of the bill drop delay)