This is great but I've noticed newer regions do not have feature parity with older ones.
For example, me-south-1 and af-south-1 still do not support AWS DataSync fully automated transfers. When this feature has been announced, it was put into 16 regions. Why not all regions where AWS DataSync is available?
There is more. This is just last example I've noticed.
As a result, when building cross-region service on AWS, it's not enough to just check whether AWS product is available in desired region, you need to check whether every single feature you need within the product is available in desired region too.
Comments
This is great but I've noticed newer regions do not have feature parity with older ones.
For example, me-south-1 and af-south-1 still do not support AWS DataSync fully automated transfers. When this feature has been announced, it was put into 16 regions. Why not all regions where AWS DataSync is available?
There is more. This is just last example I've noticed.
As a result, when building cross-region service on AWS, it's not enough to just check whether AWS product is available in desired region, you need to check whether every single feature you need within the product is available in desired region too.
I work at AWS. Region build is separate process per team and guaranteeing feature parity across all regions is a pretty complex task.