Updraft Region
Let one template behave correctly in twelve regions, without a mapping table that goes stale the next time AWS launches a region.
Multi-region templates fail in two characteristic ways. Either they carry a
Mappings block enumerating every region — which is correct on the day it is
written and wrong thereafter — or they assume every region looks like
us-east-1, and break on the first region with two availability zones or a
different DNS suffix.
These types resolve the facts at deploy time instead.
Updraft::Region::Stagger
Stagger
Overview # Deploy the same template to twelve regions and you get twelve identical schedules. Every backup starts at 03:00 UTC, every maintenance …
Updraft::Region::Metadata
Metadata
Overview # Templates that deploy to more than one region tend to accumulate a Mappings block: a hand-maintained table of region codes to availability …